Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Consolidating MS SQL Database: Things to remember?

Status
Not open for further replies.

boolean

Programmer
Mar 5, 2002
35
US
Hi,

My current assignment involves the Consolidation of 2 MS SQL 2000 database Servers into one. Most of the work that hsa been done here have been by temporary programers, who seem to have developed a lot of spread-out applications. There is a lot of redundancy and things have to be sorted out and the databases in the 2 boxes normalized and moved into one central Box.

To give you an overview of the stuff here, there are close to 30-40 different web/windows/service type applications in production and quite a lot of them are what I would rate Legacy!! not legacy applications, but apps written in VB/ASP that have existed for quite sometime... Most of the people here are not even sure which ones are used and which ones are not!

Now, the task is to concentrate at the database and reduce the 'number' as much as possible. A couple of things I would want to do right aways is to figure out if there is any way I can figure out as to when a database or a database table or a database SP or for that matter, and database entity has been lastly used. Is there a way this can be figured out??? I know that if the tables had a timestamp column on them, I could look at that but on a general perspective, is there a way an MSSQL Databases' history can be drawn out and then analyzed?

Let me know guys... Also keep posting "Things to remember" when consolidating databases/DB servers....

Thanks

Sham aka boolean... be practical/be straight... true/false?!
 
One thought:
You could put triggers on each of the tables to write to a log table each time the table is updated, inserted, or deleted. However, determining if a table has been queried can't be done with triggers.

-------------------------
The trouble with doing something right the first time is that noboby appreciates how difficult it was.
- Steven Wright
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top