for a DB on SQL server after the DB is in use?
Our old DBA allowed 3 gb for log files and we don't need nearly that
much. However, the space is still being used and reserved. Can I
shrink that "maximum" and clear up the space?
I don't want to just copy all the tables and primary keys and open a
new one with the new data, though that is plan A right now.
I cant just change sysfiles, it yells at me."John Mosey" <jmosey@.cayen.net> wrote in message
news:9e7c89ce.0311240922.462f200f@.posting.google.c om...
> Is there a fairly quick and dirty way to shrink the file size allowed
> for a DB on SQL server after the DB is in use?
> Our old DBA allowed 3 gb for log files and we don't need nearly that
> much. However, the space is still being used and reserved. Can I
> shrink that "maximum" and clear up the space?
> I don't want to just copy all the tables and primary keys and open a
> new one with the new data, though that is plan A right now.
> I cant just change sysfiles, it yells at me.
You don't mention which version of MSSQL you have - assuming it's 2000, then
you can do this through Enterprise Manager, or using DBCC SHRINKFILE.
Simon
No comments:
Post a Comment