Database Backup Security

Hi

We have developed and deployed a database which contanis very sensitive
information. Our client is now concerned about the security of the back
ups. In essense, if someone in the organization can get hold of the
backup of the database, he can simply restore it on any sql server in
the world with sa permission.

I know Microsoft provides flexibility of adding the "Password" in the
Backup t-sql statement but it wouldn't be of much use if the back up
task is saved as a script and password will be written inside the
script.

your suggestions are really appreciated!

Thanks<muzamil@.hotmail.com> wrote in message
news:1115055348.283887.64500@.z14g2000cwz.googlegro ups.com...
> Hi
> We have developed and deployed a database which contanis very sensitive
> information. Our client is now concerned about the security of the back
> ups. In essense, if someone in the organization can get hold of the
> backup of the database, he can simply restore it on any sql server in
> the world with sa permission.
> I know Microsoft provides flexibility of adding the "Password" in the
> Backup t-sql statement but it wouldn't be of much use if the back up
> task is saved as a script and password will be written inside the
> script.
> your suggestions are really appreciated!
> Thanks

If your client believes they cannot trust their own IT staff and/or cannot
secure their own backups, then I would suggest they have a number of serious
issues to address. On the technical side, they can implement a few standard
practices such as backing up to NTFS drives with appropriate ACLs, limiting
physical access to backup drives and tapes to a minimum number of trusted
staff, using OS-level auditing to see who accesses the files etc.
Ultimately, though, someone has to have access to backups, domain admin and
Exchange admin accounts etc., so they need to have people they can rely on,
and that probably isn't a problem you can or should try to solve for them -
it's really a human resources issue.

However, I appreciate that in reality, and especially in smaller companies,
these things may be not always be so easy. One possibility is to consider
encrypting the sensitive data using a key which is compiled into your
application. Your application can then encrypt/decrpyt the data when users
acess it, but if someone queries the tables directly then they only see the
encrypted data:

http://www.sqlsecurity.com/DesktopDefault.aspx?tabid=22

Simonsql

Database Architecture for keep tera byte of data

Hi

we are keeping five yeare of data which can be gone up to terabyte in size . when we are retreaving the data it will take more time to view the report .please send us the database architectur or way of keeping data to speeded up the reporting.

We have indexed the table.

Thanks

Pubudu

I recommend the Fast Terrabyte Database Architecture (patent applied for but declined) methodology. This architecture is known to be the fastest in the world. I have witnessed retrieval times faster than selecting a single record from a row of 5!! Also this method requires no indexing what-so-ever.

Unfortunately, the secret to this architecture died with it's inventor, C.J. Time. So I now recommend the Database Tuning Advisor. As for architecture, if you could provide a few more details, I'll bet some better advice would be forthcoming.

|||

Hi

I can give u a details about the database.

Thats having 25 tables.It uses for Point of Sales (pos) system.Data is comming from more than 100 branches.Therefore there can be

more than 10000 records for a day per outlet.From those all outlets data is comming to the head office database.So we are taking the

reports using centraldata base management desision making purposes.

Thanks

Pubudu

|||

10,000 records per day per outlet x 100 outlets is 1 million records per day x 220 business days per year x 5 years is ~ a billion records.

My approach would be to roll up into a data warehouse daily for analysis.

Data warehousing design

Hi

We are starting with designing a datawarehouse for my company. I have done some reading on the concepts and steps involved, but what I am seriously lacking is some examples. I'd like to read through some real examples of data warehouses that worked including the full design diagrams.
Can anyone direct me to some good sites for this?

Thanks,
TeaaZAIf you are building a true data warehouse, then get the books written by Bill Inmon. If you are building a small data mart, then you might consider Kimball's books.