March 21, 2002 at 12:13 pm
I have a 'Production' and a 'Test' SQLServer7 databases on 2 different Servers.
Let's say, I've made some changes in the design mode of the Production database. Is there any way I can track this changes on my Test database (I don't care about actual data so far).
Basically speaking, I need to see all the changes which were made on my Production server during some amount of time.
I would appreciate any help.
Alex
March 21, 2002 at 1:14 pm
I think you are doing this backwards. Any changes that you make to your production server should have already been made on your test database. That is the purpose of the test system.
Since it's already done, there isn't a good way from SQL Server to do this. RedGate has a product that will help you synch the databases.
Steve Jones
Follow me on Twitter: http://www.twitter.com/way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
March 21, 2002 at 3:26 pm
Steve,
Thank you for your advise. RedGate site looks impressive for me.
But my question will be is there a way to find out what changes were made to the Production database using SQLServer7 existing tools?
Thanks,
Alex
March 21, 2002 at 3:35 pm
If you want to look into system tables you should be able to compare them between the two servers to find the differences using a query or stored procedure.
The way to execute queries across databases is to create linked servers. Then you can execute a query that joins a table from your test server with one on your production server. If you do this with tables such as syscolumns, sysobjects, and a few others you should be able to find differences.
Robert Marda
Robert W. Marda
Billing and OSS Specialist - SQL Programmer
MCL Systems
March 22, 2002 at 7:41 am
Any idea if I can use a database log file for my purposes?
March 22, 2002 at 10:20 am
If you have a way of reading the transaction log file then you might be able to. As far as I know this will require a tool not provided by SQL Server and I don't know if any that are available will provide you with the solution you need.
Robert Marda
Robert W. Marda
Billing and OSS Specialist - SQL Programmer
MCL Systems
March 22, 2002 at 11:39 am
If you're only concerned with DDL, why not just profile it? Easier than dealing with the log.
Andy
April 1, 2002 at 5:27 am
Plus if the log is truncated you lose anything that may have been there to help. I suggest get the DDL if you need to compare what changes where made. But as for a specific time frame of when the changes were made, there is no way other than if the log holds the information. Also I suggest never make a change to your production server without making and testing in your test environment (bad practice).
"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)
April 1, 2002 at 10:45 am
Agree with above. the log is not a good choice.
Steve Jones
Follow me on Twitter: http://www.twitter.com/way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply