Need Help Shrinking WSUS 3.0 file on SBS2003
Hello,
I am running SBS2003 Standard Edition SP2. My network is very small - just three clients. One part of my backup strategy is daily backups of SBS using the built-in backup software to a Dell removable hard drive. The problem is that these daily files are too large (about 22GB). I can longer fit five of these files, along with my file backups (roughly 65GB using BackUp Exec) on one removable hard drive.
I have moved the WSUS 3.0 files (roughly 12GB worth) on another partition using wsusutil.exe. I checked my C drive and found the SUSDB.mdf file that is 5.2GB in size. If I understand correctly, this one file is almost 25% of my daily backups. I have read that this database file can be re-indexed/compacted to less than half this size. I do not understand the instructions in the other posts well enough to implement them.
If I could reduce this one file down to 2.5GB in size, for instance, it would reduce my backup space requirements by 13GB. This would be a HUGE help in my media rotation plan.
Note: I do not have SQL Server Management Studio Express installed on this server. If you think I need it, please provide a link to the correct version.
Also, besides shrinking the file, is there some way I can tell the SBS backup utility to simply skip the file? My idea is that I have one scheduled event for Mondays when I do a full backup including SUSDB.mdf. Then a second scheduled event for Tues/Wed/Thur/Frid backs up SBS while skipping the one file. This could save another 10GB or more. Or would this mess me up if I ever needed to run a restore?
Thanks so much!
I am running SBS2003 Standard Edition SP2. My network is very small - just three clients. One part of my backup strategy is daily backups of SBS using the built-in backup software to a Dell removable hard drive. The problem is that these daily files are too large (about 22GB). I can longer fit five of these files, along with my file backups (roughly 65GB using BackUp Exec) on one removable hard drive.
I have moved the WSUS 3.0 files (roughly 12GB worth) on another partition using wsusutil.exe. I checked my C drive and found the SUSDB.mdf file that is 5.2GB in size. If I understand correctly, this one file is almost 25% of my daily backups. I have read that this database file can be re-indexed/compacted to less than half this size. I do not understand the instructions in the other posts well enough to implement them.
If I could reduce this one file down to 2.5GB in size, for instance, it would reduce my backup space requirements by 13GB. This would be a HUGE help in my media rotation plan.
Note: I do not have SQL Server Management Studio Express installed on this server. If you think I need it, please provide a link to the correct version.
Also, besides shrinking the file, is there some way I can tell the SBS backup utility to simply skip the file? My idea is that I have one scheduled event for Mondays when I do a full backup including SUSDB.mdf. Then a second scheduled event for Tues/Wed/Thur/Frid backs up SBS while skipping the one file. This could save another 10GB or more. Or would this mess me up if I ever needed to run a restore?
Thanks so much!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Matt,
I need to sign off for 4 hours of so. Thanks again for your help.
I need to sign off for 4 hours of so. Thanks again for your help.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi Matt,
Sorry for the long delay in responding. Thank you again - we are getting close. I confirmed that I have WSUS 3.2 installed. I then created the WsusDBMaintenance.sql file in a text editor per your instructions and added in the location of the file in the script. I then ran a search for the sqlcmd.exe file on my server's root directory. It found the file in five locations!
1. c:\windows\SQL9_KB948109_E
2. c:\windows\SQL9_KB970892_E
3. c:\windows\SQLTools9_KB948
4. c:\windows\SQLTools9_KB970
5. c:\program files\microsoft sql server\90\tools\bin
I opened a command prompt on location #5, I copied the whole long string above, pasted it, and got an error message that SQLCMD '-I" Unknown option.
Is it possible that my sqlcmd that was already installed is an older version?
Am I supposed to type in something different at the cmd prompt or copy the sqlcmd file to the same folder of the database I am trying to reindex?
Sorry for being such a newbie with this stuff!
Sorry for the long delay in responding. Thank you again - we are getting close. I confirmed that I have WSUS 3.2 installed. I then created the WsusDBMaintenance.sql file in a text editor per your instructions and added in the location of the file in the script. I then ran a search for the sqlcmd.exe file on my server's root directory. It found the file in five locations!
1. c:\windows\SQL9_KB948109_E
2. c:\windows\SQL9_KB970892_E
3. c:\windows\SQLTools9_KB948
4. c:\windows\SQLTools9_KB970
5. c:\program files\microsoft sql server\90\tools\bin
I opened a command prompt on location #5, I copied the whole long string above, pasted it, and got an error message that SQLCMD '-I" Unknown option.
Is it possible that my sqlcmd that was already installed is an older version?
Am I supposed to type in something different at the cmd prompt or copy the sqlcmd file to the same folder of the database I am trying to reindex?
Sorry for being such a newbie with this stuff!
ASKER
Hi Matt,
I have been keeping this question open because other things have prevented me from trying out your solution. I hope to try it out in the next week or so, but decided to close the question. I will post a follow-up on the results.
I have been keeping this question open because other things have prevented me from trying out your solution. I hope to try it out in the next week or so, but decided to close the question. I will post a follow-up on the results.
ASKER
That was fast! I have a few questions:
1. How do I triple check that I have WSUS 3.0 and not 2.0? I want to be sure I don't create a huge problem.
2. How do I check if I am running Windows Internal Database? I had an IT consultant initially configure the server three years ago. He is no longer available to ask.
3. I have never used T-SQL or Visual Basic before. The page on your link shows many lines of Visual Basic. Is that something that appears when I run the script or do I need to do something in VB?
4. It says "Note: Microsoft SQL Server 2005 Command Line Query Utility requires Microsoft SQL Server Native Client, also available on this page." Do I also need to install this or is it already on my system?
5. It says I need to run the following command:
sqlcmd –I -S np:\\.\pipe\MSSQL$MICROSOF
This is completely Greek to me. Is there any way I can give you file /directory information so you could tell me exactly what I need to type? Is this risky if you have never used T-SQL before?
Sorry for the all questions. :)