Identify SQL Server databases that are no longer in use before Decommisioning

Question

Identify SQL Server databases that are no longer in use before Decommisioning

SQL learner22

Default port

Points: 1487
More actions
June 9, 2017 at 1:53 pm

#326424

all SQL server 2005 Database usage for the last month- I want to setup something that can track select and anything that users may want to do before I start shutting down the SQL server 2005- any suggestions? thanks- something like this will work for me

Viewing 9 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic. Login to reply

Eirikur Eiriksson SSC Guru Points: 182911 More actions · Answer 1

Nassan - Friday, June 9, 2017 1:53 PM
all SQL server 2005 Database usage for the last month- I want to setup something that can track select and anything that users may want to do before I start shutting down the SQL server 2005- any suggestions? thanks- something like this will work for me

Disable the logins, sit back and wait, soon you will know
😎

Sue_H SSC Guru Points: 90860 More actions · Answer 2

Probably the one I've seen most often is querying sys.dm_db_index_usage_stats to see if reads/writes are still happening to tables in the database. You wouldn't have user name though.

Sue

SQL learner22 Default port Points: 1487 More actions · Answer 3

Thanks for the feedback hope to see more feedbacks 300 of them today.
Happy fridayYYYYYYYYY

Eirikur Eiriksson SSC Guru Points: 182911 More actions · Answer 4

Nassan - Friday, June 9, 2017 2:53 PM
Thanks for the feedback hope to see more feedbacks 300 of them today.
Happy fridayYYYYYYYYY

Happy Friday and have a good weekend!
😎

Ed Wagner SSC Guru Points: 287026 More actions · Answer 5

How many users do you have? If it's a manageable number, you'd probably get a lot of mileage out of talking to them.

Sue has a great suggestion, but Eirikur's will be absolutely definitive. 😉

Tally Tables - Performance Personified
String Splitting with True Performance
Best practices on how to ask questions

SQL learner22 Default port Points: 1487 More actions · Answer 6

1st, I'm new to the org and second of all, the instance got about 50 Dbs and users are many and I don't want to chase people I don't know specially when they are hundreds.
thanks.

I wanted a simple script that I can turn into sp and create one table and agent job that runs ones a day for few months and INSERT 1 record per DB a day and I can check whatsup few months later. of course share that with management and get final approval of what I want to do which get rid of the instances.

Eirikur Eiriksson SSC Guru Points: 182911 More actions · Answer 7

Nassan - Friday, June 9, 2017 3:41 PM
1st, I'm new to the org and second of all, the instance got about 50 Dbs and users are many and I don't want to chase people I don't know specially when they are hundreds.
thanks.
I wanted a simple script that I can turn into sp and create one table and agent job that runs ones a day for few months and INSERT 1 record per DB a day and I can check whatsup few months later. of course share that with management and get final approval of what I want to do which get rid of the instances.

What about "the most important" database that's updated once every year etc?
😎

Ed Wagner SSC Guru Points: 287026 More actions · Answer 8

Eirikur Eiriksson - Friday, June 9, 2017 11:46 PM
Nassan - Friday, June 9, 2017 3:41 PM
1st, I'm new to the org and second of all, the instance got about 50 Dbs and users are many and I don't want to chase people I don't know specially when they are hundreds.
thanks.
I wanted a simple script that I can turn into sp and create one table and agent job that runs ones a day for few months and INSERT 1 record per DB a day and I can check whatsup few months later. of course share that with management and get final approval of what I want to do which get rid of the instances.
What about "the most important" database that's updated once every year etc?
😎

With my SQL 2005 retirement I did last year, I didn't have the one database that was updated once a year. I had the database where the application (which was central to a critical business operation) wouldn't connect to SQL 2008. Naturally, an application upgrade was available, but we'd have to buy it outright because we didn't keep up with the maintenance and support plan. The hardware was also outdated and we can't even get parts for it any more, so we'd have to buy new stuff. The final price tag was deemed "not economically viable" so we stayed with what we had. So, our SQL 2005 instance still exists to support a single database. I'm ready if the server dies, but don't ask what happens when the hardware fails. So much for a critical operation, right? :crazy:

Tally Tables - Performance Personified
String Splitting with True Performance
Best practices on how to ask questions