Hey Guys --
We have a database that gets lots of activity, but it's not mission
critical data, so no need for a backup. Problem is the Transaction Log
was set to Automatically Grow, and over a year or so it grew to over 50
gigs and filled-up the HD.
We did a backup and the transaction log is down now, but the Space
Allocated is still sitting at 50 Gigs and locking that space for
transaction logs not leaving any room for anything else. How can I
change this? I went into the DB properties and tried to change the
Space Allocated to like 100 (Megs) but I get the error: The new DBFile
size must be larger than the current size. How can I reduce this
filesize?
Thanks for any insight or ideas.
Sam
You can shrink the file using DBCC SHRINKFILE. See the Books Online for
details.
Also, assuming SQL 2000, change the database recovery model to SIMPLE if you
don't need the transaction log for recovery.
> We have a database that gets lots of activity, but it's not mission
> critical data, so no need for a backup.
Do you mean transaction log backup? If you perform no full database
backups, your only option in the event of database loss is to recreate the
database from script.
Hope this helps.
Dan Guzman
SQL Server MVP
"Alex" <samalex@.gmail.com> wrote in message
news:1134491880.285851.217750@.g44g2000cwa.googlegr oups.com...
> Hey Guys --
> We have a database that gets lots of activity, but it's not mission
> critical data, so no need for a backup. Problem is the Transaction Log
> was set to Automatically Grow, and over a year or so it grew to over 50
> gigs and filled-up the HD.
> We did a backup and the transaction log is down now, but the Space
> Allocated is still sitting at 50 Gigs and locking that space for
> transaction logs not leaving any room for anything else. How can I
> change this? I went into the DB properties and tried to change the
> Space Allocated to like 100 (Megs) but I get the error: The new DBFile
> size must be larger than the current size. How can I reduce this
> filesize?
> Thanks for any insight or ideas.
> Sam
>
|||Shrink that pig !
Backup T-Log
DBCC SHRINKFILE(FIleName,0)
Change Growth Settings...
"Alex" <samalex@.gmail.com> wrote in message
news:1134491880.285851.217750@.g44g2000cwa.googlegr oups.com...
> Hey Guys --
> We have a database that gets lots of activity, but it's not mission
> critical data, so no need for a backup. Problem is the Transaction Log
> was set to Automatically Grow, and over a year or so it grew to over 50
> gigs and filled-up the HD.
> We did a backup and the transaction log is down now, but the Space
> Allocated is still sitting at 50 Gigs and locking that space for
> transaction logs not leaving any room for anything else. How can I
> change this? I went into the DB properties and tried to change the
> Space Allocated to like 100 (Megs) but I get the error: The new DBFile
> size must be larger than the current size. How can I reduce this
> filesize?
> Thanks for any insight or ideas.
> Sam
>
Showing posts with label allocated. Show all posts
Showing posts with label allocated. Show all posts
Saturday, February 25, 2012
Reduce the 'Space Allocated' for Transaction Logs in MS SQL 2K
Hey Guys --
We have a database that gets lots of activity, but it's not mission
critical data, so no need for a backup. Problem is the Transaction Log
was set to Automatically Grow, and over a year or so it grew to over 50
gigs and filled-up the HD.
We did a backup and the transaction log is down now, but the Space
Allocated is still sitting at 50 Gigs and locking that space for
transaction logs not leaving any room for anything else. How can I
change this? I went into the DB properties and tried to change the
Space Allocated to like 100 (Megs) but I get the error: The new DBFile
size must be larger than the current size. How can I reduce this
filesize?
Thanks for any insight or ideas.
SamYou can shrink the file using DBCC SHRINKFILE. See the Books Online for
details.
Also, assuming SQL 2000, change the database recovery model to SIMPLE if you
don't need the transaction log for recovery.
> We have a database that gets lots of activity, but it's not mission
> critical data, so no need for a backup.
Do you mean transaction log backup? If you perform no full database
backups, your only option in the event of database loss is to recreate the
database from script.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Alex" <samalex@.gmail.com> wrote in message
news:1134491880.285851.217750@.g44g2000cwa.googlegroups.com...
> Hey Guys --
> We have a database that gets lots of activity, but it's not mission
> critical data, so no need for a backup. Problem is the Transaction Log
> was set to Automatically Grow, and over a year or so it grew to over 50
> gigs and filled-up the HD.
> We did a backup and the transaction log is down now, but the Space
> Allocated is still sitting at 50 Gigs and locking that space for
> transaction logs not leaving any room for anything else. How can I
> change this? I went into the DB properties and tried to change the
> Space Allocated to like 100 (Megs) but I get the error: The new DBFile
> size must be larger than the current size. How can I reduce this
> filesize?
> Thanks for any insight or ideas.
> Sam
>|||Shrink that pig !
Backup T-Log
DBCC SHRINKFILE(FIleName,0)
Change Growth Settings...
"Alex" <samalex@.gmail.com> wrote in message
news:1134491880.285851.217750@.g44g2000cwa.googlegroups.com...
> Hey Guys --
> We have a database that gets lots of activity, but it's not mission
> critical data, so no need for a backup. Problem is the Transaction Log
> was set to Automatically Grow, and over a year or so it grew to over 50
> gigs and filled-up the HD.
> We did a backup and the transaction log is down now, but the Space
> Allocated is still sitting at 50 Gigs and locking that space for
> transaction logs not leaving any room for anything else. How can I
> change this? I went into the DB properties and tried to change the
> Space Allocated to like 100 (Megs) but I get the error: The new DBFile
> size must be larger than the current size. How can I reduce this
> filesize?
> Thanks for any insight or ideas.
> Sam
>
We have a database that gets lots of activity, but it's not mission
critical data, so no need for a backup. Problem is the Transaction Log
was set to Automatically Grow, and over a year or so it grew to over 50
gigs and filled-up the HD.
We did a backup and the transaction log is down now, but the Space
Allocated is still sitting at 50 Gigs and locking that space for
transaction logs not leaving any room for anything else. How can I
change this? I went into the DB properties and tried to change the
Space Allocated to like 100 (Megs) but I get the error: The new DBFile
size must be larger than the current size. How can I reduce this
filesize?
Thanks for any insight or ideas.
SamYou can shrink the file using DBCC SHRINKFILE. See the Books Online for
details.
Also, assuming SQL 2000, change the database recovery model to SIMPLE if you
don't need the transaction log for recovery.
> We have a database that gets lots of activity, but it's not mission
> critical data, so no need for a backup.
Do you mean transaction log backup? If you perform no full database
backups, your only option in the event of database loss is to recreate the
database from script.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Alex" <samalex@.gmail.com> wrote in message
news:1134491880.285851.217750@.g44g2000cwa.googlegroups.com...
> Hey Guys --
> We have a database that gets lots of activity, but it's not mission
> critical data, so no need for a backup. Problem is the Transaction Log
> was set to Automatically Grow, and over a year or so it grew to over 50
> gigs and filled-up the HD.
> We did a backup and the transaction log is down now, but the Space
> Allocated is still sitting at 50 Gigs and locking that space for
> transaction logs not leaving any room for anything else. How can I
> change this? I went into the DB properties and tried to change the
> Space Allocated to like 100 (Megs) but I get the error: The new DBFile
> size must be larger than the current size. How can I reduce this
> filesize?
> Thanks for any insight or ideas.
> Sam
>|||Shrink that pig !
Backup T-Log
DBCC SHRINKFILE(FIleName,0)
Change Growth Settings...
"Alex" <samalex@.gmail.com> wrote in message
news:1134491880.285851.217750@.g44g2000cwa.googlegroups.com...
> Hey Guys --
> We have a database that gets lots of activity, but it's not mission
> critical data, so no need for a backup. Problem is the Transaction Log
> was set to Automatically Grow, and over a year or so it grew to over 50
> gigs and filled-up the HD.
> We did a backup and the transaction log is down now, but the Space
> Allocated is still sitting at 50 Gigs and locking that space for
> transaction logs not leaving any room for anything else. How can I
> change this? I went into the DB properties and tried to change the
> Space Allocated to like 100 (Megs) but I get the error: The new DBFile
> size must be larger than the current size. How can I reduce this
> filesize?
> Thanks for any insight or ideas.
> Sam
>
Reduce the 'Space Allocated' for Transaction Logs in MS SQL 2K
Hey Guys --
We have a database that gets lots of activity, but it's not mission
critical data, so no need for a backup. Problem is the Transaction Log
was set to Automatically Grow, and over a year or so it grew to over 50
gigs and filled-up the HD.
We did a backup and the transaction log is down now, but the Space
Allocated is still sitting at 50 Gigs and locking that space for
transaction logs not leaving any room for anything else. How can I
change this? I went into the DB properties and tried to change the
Space Allocated to like 100 (Megs) but I get the error: The new DBFile
size must be larger than the current size. How can I reduce this
filesize?
Thanks for any insight or ideas.
SamYou can shrink the file using DBCC SHRINKFILE. See the Books Online for
details.
Also, assuming SQL 2000, change the database recovery model to SIMPLE if you
don't need the transaction log for recovery.
> We have a database that gets lots of activity, but it's not mission
> critical data, so no need for a backup.
Do you mean transaction log backup? If you perform no full database
backups, your only option in the event of database loss is to recreate the
database from script.
Hope this helps.
Dan Guzman
SQL Server MVP
"Alex" <samalex@.gmail.com> wrote in message
news:1134491880.285851.217750@.g44g2000cwa.googlegroups.com...
> Hey Guys --
> We have a database that gets lots of activity, but it's not mission
> critical data, so no need for a backup. Problem is the Transaction Log
> was set to Automatically Grow, and over a year or so it grew to over 50
> gigs and filled-up the HD.
> We did a backup and the transaction log is down now, but the Space
> Allocated is still sitting at 50 Gigs and locking that space for
> transaction logs not leaving any room for anything else. How can I
> change this? I went into the DB properties and tried to change the
> Space Allocated to like 100 (Megs) but I get the error: The new DBFile
> size must be larger than the current size. How can I reduce this
> filesize?
> Thanks for any insight or ideas.
> Sam
>|||Shrink that pig !
Backup T-Log
DBCC SHRINKFILE(FIleName,0)
Change Growth Settings...
"Alex" <samalex@.gmail.com> wrote in message
news:1134491880.285851.217750@.g44g2000cwa.googlegroups.com...
> Hey Guys --
> We have a database that gets lots of activity, but it's not mission
> critical data, so no need for a backup. Problem is the Transaction Log
> was set to Automatically Grow, and over a year or so it grew to over 50
> gigs and filled-up the HD.
> We did a backup and the transaction log is down now, but the Space
> Allocated is still sitting at 50 Gigs and locking that space for
> transaction logs not leaving any room for anything else. How can I
> change this? I went into the DB properties and tried to change the
> Space Allocated to like 100 (Megs) but I get the error: The new DBFile
> size must be larger than the current size. How can I reduce this
> filesize?
> Thanks for any insight or ideas.
> Sam
>
We have a database that gets lots of activity, but it's not mission
critical data, so no need for a backup. Problem is the Transaction Log
was set to Automatically Grow, and over a year or so it grew to over 50
gigs and filled-up the HD.
We did a backup and the transaction log is down now, but the Space
Allocated is still sitting at 50 Gigs and locking that space for
transaction logs not leaving any room for anything else. How can I
change this? I went into the DB properties and tried to change the
Space Allocated to like 100 (Megs) but I get the error: The new DBFile
size must be larger than the current size. How can I reduce this
filesize?
Thanks for any insight or ideas.
SamYou can shrink the file using DBCC SHRINKFILE. See the Books Online for
details.
Also, assuming SQL 2000, change the database recovery model to SIMPLE if you
don't need the transaction log for recovery.
> We have a database that gets lots of activity, but it's not mission
> critical data, so no need for a backup.
Do you mean transaction log backup? If you perform no full database
backups, your only option in the event of database loss is to recreate the
database from script.
Hope this helps.
Dan Guzman
SQL Server MVP
"Alex" <samalex@.gmail.com> wrote in message
news:1134491880.285851.217750@.g44g2000cwa.googlegroups.com...
> Hey Guys --
> We have a database that gets lots of activity, but it's not mission
> critical data, so no need for a backup. Problem is the Transaction Log
> was set to Automatically Grow, and over a year or so it grew to over 50
> gigs and filled-up the HD.
> We did a backup and the transaction log is down now, but the Space
> Allocated is still sitting at 50 Gigs and locking that space for
> transaction logs not leaving any room for anything else. How can I
> change this? I went into the DB properties and tried to change the
> Space Allocated to like 100 (Megs) but I get the error: The new DBFile
> size must be larger than the current size. How can I reduce this
> filesize?
> Thanks for any insight or ideas.
> Sam
>|||Shrink that pig !
Backup T-Log
DBCC SHRINKFILE(FIleName,0)
Change Growth Settings...
"Alex" <samalex@.gmail.com> wrote in message
news:1134491880.285851.217750@.g44g2000cwa.googlegroups.com...
> Hey Guys --
> We have a database that gets lots of activity, but it's not mission
> critical data, so no need for a backup. Problem is the Transaction Log
> was set to Automatically Grow, and over a year or so it grew to over 50
> gigs and filled-up the HD.
> We did a backup and the transaction log is down now, but the Space
> Allocated is still sitting at 50 Gigs and locking that space for
> transaction logs not leaving any room for anything else. How can I
> change this? I went into the DB properties and tried to change the
> Space Allocated to like 100 (Megs) but I get the error: The new DBFile
> size must be larger than the current size. How can I reduce this
> filesize?
> Thanks for any insight or ideas.
> Sam
>
Monday, February 20, 2012
Reduce size allocated to a database
We have allocated 10GB to a production database in SQL Server 2000 and we
find that it only uses around 600MB in size.
Can we change the size allocated from 10GB to say 3GB ? Is there any steps
we have to perform before the change ? Does the benefit of changing the
size is only saving in disk space ?
Thanks
Mark
If you want to reduce a physical size if the database , so run DBCC
SHRINKFILE command
"Mark" <Mark@.discussions.microsoft.com> wrote in message
news:OjMhzkj%23FHA.3036@.TK2MSFTNGP09.phx.gbl...
> We have allocated 10GB to a production database in SQL Server 2000 and we
> find that it only uses around 600MB in size.
> Can we change the size allocated from 10GB to say 3GB ? Is there any
> steps we have to perform before the change ? Does the benefit of changing
> the size is only saving in disk space ?
> Thanks
>
|||> Does the benefit of changing the size is only saving in disk space ?
Yes. You pay no penalty for having a large database file with SQL Server. Some additional comments
about shrink: http://www.karaszi.com/SQLServer/info_dont_shrink.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Mark" <Mark@.discussions.microsoft.com> wrote in message
news:OjMhzkj%23FHA.3036@.TK2MSFTNGP09.phx.gbl...
> We have allocated 10GB to a production database in SQL Server 2000 and we find that it only uses
> around 600MB in size.
> Can we change the size allocated from 10GB to say 3GB ? Is there any steps we have to perform
> before the change ? Does the benefit of changing the size is only saving in disk space ?
> Thanks
>
|||Dear Uri,
Do you mean that after changing the Database file size, I have to run DBCC
SHRINKFILE ?
Thanks
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:OAOaG8j%23FHA.2452@.TK2MSFTNGP11.phx.gbl...
> Mark
> If you want to reduce a physical size if the database , so run DBCC
> SHRINKFILE command
>
>
> "Mark" <Mark@.discussions.microsoft.com> wrote in message
> news:OjMhzkj%23FHA.3036@.TK2MSFTNGP09.phx.gbl...
>
find that it only uses around 600MB in size.
Can we change the size allocated from 10GB to say 3GB ? Is there any steps
we have to perform before the change ? Does the benefit of changing the
size is only saving in disk space ?
Thanks
Mark
If you want to reduce a physical size if the database , so run DBCC
SHRINKFILE command
"Mark" <Mark@.discussions.microsoft.com> wrote in message
news:OjMhzkj%23FHA.3036@.TK2MSFTNGP09.phx.gbl...
> We have allocated 10GB to a production database in SQL Server 2000 and we
> find that it only uses around 600MB in size.
> Can we change the size allocated from 10GB to say 3GB ? Is there any
> steps we have to perform before the change ? Does the benefit of changing
> the size is only saving in disk space ?
> Thanks
>
|||> Does the benefit of changing the size is only saving in disk space ?
Yes. You pay no penalty for having a large database file with SQL Server. Some additional comments
about shrink: http://www.karaszi.com/SQLServer/info_dont_shrink.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Mark" <Mark@.discussions.microsoft.com> wrote in message
news:OjMhzkj%23FHA.3036@.TK2MSFTNGP09.phx.gbl...
> We have allocated 10GB to a production database in SQL Server 2000 and we find that it only uses
> around 600MB in size.
> Can we change the size allocated from 10GB to say 3GB ? Is there any steps we have to perform
> before the change ? Does the benefit of changing the size is only saving in disk space ?
> Thanks
>
|||Dear Uri,
Do you mean that after changing the Database file size, I have to run DBCC
SHRINKFILE ?
Thanks
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:OAOaG8j%23FHA.2452@.TK2MSFTNGP11.phx.gbl...
> Mark
> If you want to reduce a physical size if the database , so run DBCC
> SHRINKFILE command
>
>
> "Mark" <Mark@.discussions.microsoft.com> wrote in message
> news:OjMhzkj%23FHA.3036@.TK2MSFTNGP09.phx.gbl...
>
Reduce size allocated to a database
We have allocated 10GB to a production database in SQL Server 2000 and we
find that it only uses around 600MB in size.
Can we change the size allocated from 10GB to say 3GB ? Is there any steps
we have to perform before the change ? Does the benefit of changing the
size is only saving in disk space ?
ThanksMark
If you want to reduce a physical size if the database , so run DBCC
SHRINKFILE command
"Mark" <Mark@.discussions.microsoft.com> wrote in message
news:OjMhzkj%23FHA.3036@.TK2MSFTNGP09.phx.gbl...
> We have allocated 10GB to a production database in SQL Server 2000 and we
> find that it only uses around 600MB in size.
> Can we change the size allocated from 10GB to say 3GB ? Is there any
> steps we have to perform before the change ? Does the benefit of changing
> the size is only saving in disk space ?
> Thanks
>|||> Does the benefit of changing the size is only saving in disk space ?
Yes. You pay no penalty for having a large database file with SQL Server. Some additional comments
about shrink: http://www.karaszi.com/SQLServer/info_dont_shrink.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Mark" <Mark@.discussions.microsoft.com> wrote in message
news:OjMhzkj%23FHA.3036@.TK2MSFTNGP09.phx.gbl...
> We have allocated 10GB to a production database in SQL Server 2000 and we find that it only uses
> around 600MB in size.
> Can we change the size allocated from 10GB to say 3GB ? Is there any steps we have to perform
> before the change ? Does the benefit of changing the size is only saving in disk space ?
> Thanks
>|||Dear Uri,
Do you mean that after changing the Database file size, I have to run DBCC
SHRINKFILE ?
Thanks
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:OAOaG8j%23FHA.2452@.TK2MSFTNGP11.phx.gbl...
> Mark
> If you want to reduce a physical size if the database , so run DBCC
> SHRINKFILE command
>
>
> "Mark" <Mark@.discussions.microsoft.com> wrote in message
> news:OjMhzkj%23FHA.3036@.TK2MSFTNGP09.phx.gbl...
>> We have allocated 10GB to a production database in SQL Server 2000 and we
>> find that it only uses around 600MB in size.
>> Can we change the size allocated from 10GB to say 3GB ? Is there any
>> steps we have to perform before the change ? Does the benefit of
>> changing the size is only saving in disk space ?
>> Thanks
>
find that it only uses around 600MB in size.
Can we change the size allocated from 10GB to say 3GB ? Is there any steps
we have to perform before the change ? Does the benefit of changing the
size is only saving in disk space ?
ThanksMark
If you want to reduce a physical size if the database , so run DBCC
SHRINKFILE command
"Mark" <Mark@.discussions.microsoft.com> wrote in message
news:OjMhzkj%23FHA.3036@.TK2MSFTNGP09.phx.gbl...
> We have allocated 10GB to a production database in SQL Server 2000 and we
> find that it only uses around 600MB in size.
> Can we change the size allocated from 10GB to say 3GB ? Is there any
> steps we have to perform before the change ? Does the benefit of changing
> the size is only saving in disk space ?
> Thanks
>|||> Does the benefit of changing the size is only saving in disk space ?
Yes. You pay no penalty for having a large database file with SQL Server. Some additional comments
about shrink: http://www.karaszi.com/SQLServer/info_dont_shrink.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Mark" <Mark@.discussions.microsoft.com> wrote in message
news:OjMhzkj%23FHA.3036@.TK2MSFTNGP09.phx.gbl...
> We have allocated 10GB to a production database in SQL Server 2000 and we find that it only uses
> around 600MB in size.
> Can we change the size allocated from 10GB to say 3GB ? Is there any steps we have to perform
> before the change ? Does the benefit of changing the size is only saving in disk space ?
> Thanks
>|||Dear Uri,
Do you mean that after changing the Database file size, I have to run DBCC
SHRINKFILE ?
Thanks
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:OAOaG8j%23FHA.2452@.TK2MSFTNGP11.phx.gbl...
> Mark
> If you want to reduce a physical size if the database , so run DBCC
> SHRINKFILE command
>
>
> "Mark" <Mark@.discussions.microsoft.com> wrote in message
> news:OjMhzkj%23FHA.3036@.TK2MSFTNGP09.phx.gbl...
>> We have allocated 10GB to a production database in SQL Server 2000 and we
>> find that it only uses around 600MB in size.
>> Can we change the size allocated from 10GB to say 3GB ? Is there any
>> steps we have to perform before the change ? Does the benefit of
>> changing the size is only saving in disk space ?
>> Thanks
>
Reduce size allocated to a database
We have allocated 10GB to a production database in SQL Server 2000 and we
find that it only uses around 600MB in size.
Can we change the size allocated from 10GB to say 3GB ? Is there any steps
we have to perform before the change ? Does the benefit of changing the
size is only saving in disk space ?
ThanksMark
If you want to reduce a physical size if the database , so run DBCC
SHRINKFILE command
"Mark" <Mark@.discussions.microsoft.com> wrote in message
news:OjMhzkj%23FHA.3036@.TK2MSFTNGP09.phx.gbl...
> We have allocated 10GB to a production database in SQL Server 2000 and we
> find that it only uses around 600MB in size.
> Can we change the size allocated from 10GB to say 3GB ? Is there any
> steps we have to perform before the change ? Does the benefit of changing
> the size is only saving in disk space ?
> Thanks
>|||> Does the benefit of changing the size is only saving in disk space ?
Yes. You pay no penalty for having a large database file with SQL Server. So
me additional comments
about shrink: http://www.karaszi.com/SQLServer/info_dont_shrink.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Mark" <Mark@.discussions.microsoft.com> wrote in message
news:OjMhzkj%23FHA.3036@.TK2MSFTNGP09.phx.gbl...
> We have allocated 10GB to a production database in SQL Server 2000 and we
find that it only uses
> around 600MB in size.
> Can we change the size allocated from 10GB to say 3GB ? Is there any step
s we have to perform
> before the change ? Does the benefit of changing the size is only saving
in disk space ?
> Thanks
>|||Dear Uri,
Do you mean that after changing the Database file size, I have to run DBCC
SHRINKFILE ?
Thanks
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:OAOaG8j%23FHA.2452@.TK2MSFTNGP11.phx.gbl...
> Mark
> If you want to reduce a physical size if the database , so run DBCC
> SHRINKFILE command
>
>
> "Mark" <Mark@.discussions.microsoft.com> wrote in message
> news:OjMhzkj%23FHA.3036@.TK2MSFTNGP09.phx.gbl...
>
find that it only uses around 600MB in size.
Can we change the size allocated from 10GB to say 3GB ? Is there any steps
we have to perform before the change ? Does the benefit of changing the
size is only saving in disk space ?
ThanksMark
If you want to reduce a physical size if the database , so run DBCC
SHRINKFILE command
"Mark" <Mark@.discussions.microsoft.com> wrote in message
news:OjMhzkj%23FHA.3036@.TK2MSFTNGP09.phx.gbl...
> We have allocated 10GB to a production database in SQL Server 2000 and we
> find that it only uses around 600MB in size.
> Can we change the size allocated from 10GB to say 3GB ? Is there any
> steps we have to perform before the change ? Does the benefit of changing
> the size is only saving in disk space ?
> Thanks
>|||> Does the benefit of changing the size is only saving in disk space ?
Yes. You pay no penalty for having a large database file with SQL Server. So
me additional comments
about shrink: http://www.karaszi.com/SQLServer/info_dont_shrink.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Mark" <Mark@.discussions.microsoft.com> wrote in message
news:OjMhzkj%23FHA.3036@.TK2MSFTNGP09.phx.gbl...
> We have allocated 10GB to a production database in SQL Server 2000 and we
find that it only uses
> around 600MB in size.
> Can we change the size allocated from 10GB to say 3GB ? Is there any step
s we have to perform
> before the change ? Does the benefit of changing the size is only saving
in disk space ?
> Thanks
>|||Dear Uri,
Do you mean that after changing the Database file size, I have to run DBCC
SHRINKFILE ?
Thanks
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:OAOaG8j%23FHA.2452@.TK2MSFTNGP11.phx.gbl...
> Mark
> If you want to reduce a physical size if the database , so run DBCC
> SHRINKFILE command
>
>
> "Mark" <Mark@.discussions.microsoft.com> wrote in message
> news:OjMhzkj%23FHA.3036@.TK2MSFTNGP09.phx.gbl...
>
Subscribe to:
Posts (Atom)