Posted by: Colin Smith
Clean Up, MS SQL, MS SQL Admin, Powershell, SQL Server
A few months ago I was transferred to my companies parent company. I think that this is good news for me so I am happy about it now. I have been asking, for about a month, to do a network scan in order to identify servers that have SQL installed. Due to the holidays and scheduling I did not get this right away. I just got a list today and so I wanted to get going and see what I have to deal with. First of all I have 142 servers that have been identified on the scanned networks, more to come, that I have to start looking into. I have a script that will go out and get some basic information about each instance as long as I have an instance name. I do not, I only have the host name of the servers. That is OK though as I think most are default instances. Anyway, I started my script and away it went. It scanned about 5 servers before running into one that is not a default instance. Because of this I will write another script tomorrow to go get all the instance names. I will try to post that script as well. Before it stopped though, I found one server with 117 Databases on it. WOW. It is also running SQL Server 2000. I am not really happy about that. Also, I see one Database is about 6 gigs and has a log file that is actually larger then the database file.
All that being said I think that I am going to have a lot of work to do in the next couple of months. Should be fun though and I am sure that I will run into some things that I have never seen before. You know, like a SQL Server 2000 instance with over 100 databases on it.
I will try to get a script together to find all the instances and when I do I will post it here. I will also post on some of the things that I find over the next few weeks and I will post how I handled some of the issues that I run into. Like I said, should be a blast and perhaps this is really what I needed to get the passion back.