December 26, 2006 at 4:38 pm
We have a website that accesses our SQL databases. In the past, we used our internal employees to improve our SQL databases. However, we want to outsource the work.
There is a lot of information we would like to keep private from the outsourcing.
I found this product through Google…
http://www.sqlmanager.net/en/products/mssql/datagenerator
Would this program help us make test data?
Thanks in advance
-Devin
December 26, 2006 at 5:16 pm
My guess is you are asking about schema change...
In sql 2005 you can use DDL trigger to keep track of schema changes where in 2000 there is not built in option..
In sql 2000 you install SQL audit tools like Entegra to monitor ddl changes...
http://www.lumigent.com/products/auditdb.html
http://www.sql-server-performance.com/entegra_spotlight.asp
MohammedU
Microsoft SQL Server MVP
December 27, 2006 at 12:59 am
Check out Data Dude ! Visual Studio Team for DBAs ! Still in CTP, but very valuable for schema-maintenance AND test-data-generation !
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data and code to get the best help
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
December 27, 2006 at 9:29 am
The other thing you can do is write some obfuscation scripts and backup/restore production, then run the script to change data that might be identifieable, names, SSNs, salaries, whatever.
December 27, 2006 at 11:35 am
Thanks for the quick responses
We have two complete databases right now:
One for the original
Another for the testing with the test data
Could I use the DDL trigger to monitor schema changes and then somehow move those changes to the original?
Could you point me in the correct direction to make a DDL trigger like this?
December 27, 2006 at 6:48 pm
Yes you can monitor ddl changes using ddl triggers but in 2005 not in 2000...
Check SQL server 2005 BOL
http://msdn2.microsoft.com/en-us/library/ms186406.aspx
MohammedU
Microsoft SQL Server MVP
December 28, 2006 at 12:11 pm
You want to keep everything separated between the two databases. You certainly don't want a mechanism that automatically updates the production database with changes made in the test/dev database. Everybody makes mistakes, you don't want simple mistakes in dev/test to take down your production system. In fact, they shouldn't even be on the same server since there may be server settings that need to be changed.
When everything is complete and ready to be moved to production, ALL changes should be scripted out. All schema changes and all data changes should be scripted. Do not import data directly from dev/test to production, write scripts to change or populate the data.
If the outsource person or company can not handle that simple standard, then they are not the ones for the job.
Once everything is scripted out and ready to deploy, backfill the test database from production again (backup/restore), run your data sanitization scripts, and then test the deployment scripts. Repeat until the deployment scripts work without a hitch.
If you do otherwise, you are headed for heartache sooner or later. The kind of heartache that causes lawsuits and lost jobs.
Viewing 7 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply