I'm looking to make some space on my SIMS server. Is it ok to delete the old SQL folders (MSSQL.1 and MSSQL$SIMS) leaving just the MSSQL10.SIMS2008 folder. Also deleteing some of the older .bak files ok?
Printable View
I'm looking to make some space on my SIMS server. Is it ok to delete the old SQL folders (MSSQL.1 and MSSQL$SIMS) leaving just the MSSQL10.SIMS2008 folder. Also deleteing some of the older .bak files ok?
This sort of stuff always scares me, not matter how much you're told it's okay. So i would say, yes it should be, but make decent backups before hand.
Make sure you don't run anything on the older SQL. I take it this is a relic of the move from 2005 to 2008. Part of that process should have been to turn off the old services, which will be a good indication that it's all safe to remove. Rather than delete, you should actually uninstall the old SQL, but that could be scary, in case it removes something shared that the current one requires. I know that i just went for a clean install on a new machine to make sure it was all clear. I noticed that the SQL 2k8 R2 install on Server 2k8 R2, still created a load of files in the Program Files (x86) folder and some of them were required for comms, so it's not as easy as 'delete what looks old'. If it's space you want, and you still have the old SIMS present, you could remove the SIMS mdf / ldf from the old folder, and any other .bak files. Hopefully that will clear some.
Removing old .bak files is okay, so long as you're happy with what you're left with in case you need access to old data. You can zip others, i normally reduce 3.5GB to 1GB ish, which saves a fair amount.
I'd look to moving to a new (ideally virtual) server. It's also a good test of what you might do in a disaster recovery situation.
Can you get some external storage and move old files instead of deleting them? That way if something does screw up you have a lifeline.
Go into Add\Remove programs, remove Microsoft SQL 2005, when the uninstaller loads, remove the sims2005 instance, leave the workstation components, then repeat for MSDE - if you miss the service manager get this -> SQL 2005 Service ManagerQuote:
Originally Posted by chazzy2501
Once it's uninstalled - remove the mssql.1 and mssql$sims folders.
I removed the workstation components, (oops) is that a big deal?
I've got the server snapshotted should I role back?
Should be ok, check FMS. If it doesn't work install the SQL 2005 Native client then run FMSApplicationSetup.exe again.
(Can't remember if Native client comes under workstation tools).
I just rolled back, the first time I've ever used it properly. I am impressed! Even the icons are back where I left them. It took just 30 seconds :)
I'll uninstall again and read the advise fully this time.
Good test then, it did what it said on the tin :)
BTW what is FMS? I don't think we use it.
FMS is a financial management system by Capita. Its separate to SIMS.net.Quote:
Originally Posted by chazzy2501
Couldn't find a MSDE and 2005 is out but I can't delete either of the mssql$sims or the mssql.1 folders. I get an access denied on a opends60.dll
reboot?
Microsoft SQL Server Data Engine - Might have SIMS in the name, can't remember, it's been so long since I've last seen it!!
wowser, the backup files have grown in the last few years, 200mb ~ 300mb each in 2007 to 2.2gb each in 2011.
got rid of 5 (leaving 5) new ones and created over 10GB of space. (I was down to my last 600mb) few, Time to install discover.
have you got @matt40k's Tidybackup routine running. This will zip the backups down and can be set to delete after a certain timeQuote:
Originally Posted by chazzy2501
I thought MSDE was the free pseudo SQL thingy that came with Office Pro, or something like that. OR is that just what SQL Express installs as.
I'm really hoping the backups you're talking of are just the ones that SIMS does when you upgrade. Don't really need much management. Hopefully you have daily backups going somewhere safe, like a shared drive that then gets dumped to tape. That's where it's really useful to have TidyBackups.