DB Engine :: Why Does Log File Grow When Recovery Mode Is Simple

Jul 30, 2015

My understanding is that the log file is not supposed to grow if the database is under simple recovery mode.I am in a situation where the log grows if do any inserts that involve millions of rows.How do i make sure that it does not grow?

View 11 Replies


ADVERTISEMENT

DB Engine :: Simple Recovery Mode - Log Size Increases

Jun 2, 2015

Is this Possible, If database is in Simple recovery Mode and the ldf size gets increased?? .

mdf size :  159 GB (171,383,717,888 bytes)
ldf size : 6.46 GB (6,945,505,280 bytes).

My question is if the recovery model is in Simple Mode then why the log gets generated high.

dbcc sqlperf(logspace) --output
DATABASE  Logsize(MB)      Log space used(%)     status
mam         6623.742
        0.4305579
             0

Is there any issue or it is Normal.

View 9 Replies View Related

What Is Simple Recovery Mode?

Jun 5, 2007

Hi,

On SQL 2000, if I have a large transaction log for my database and I manage to fill it with a single large transaction but it is not set to autogrow, what happens?

View 6 Replies View Related

Recovery Mode SIMPLE && SP2

Mar 12, 2007

I have several databases that perform daily backups. Ever since I installed SP2, the backup jobs are failing. The logs state that it's because the database recovery mode cannot be SIMPLE, but need to be either FULL or Bulk-Logged.

Can anyone tell me if this is true, and that I do have to change my recovery mode?

Here's the error:

NEW COMPONENT OUTPUT
Microsoft(R) Server Maintenance Utility (Unicode) Version 9.0.3042
Report was generated on "ICIS-SQL-SERVER".
Maintenance Plan: DB Backup
Duration: 00:08:05
Status: Warning: One or more tasks failed..
Details:
Back Up Database (Transaction Log) (ICIS-SQL-SERVER)
Backup Database on Target server connection
Databases that have a compatibility level of 70 (SQL Server version 7.0) will be skipped.
Databases: All user databases
Type: Transaction Log
Append existing
Task start: 2007-03-10T05:08:09.
Task end: 2007-03-10T05:08:09.
Failed:(-1073548784) Executing the query "BACKUP LOG [hl7 db_SamirTesting] TO DISK = N'D:\mssql\backup\hl7 db_SamirTesting\hl7 db_SamirTesting_backup_200703100508.trn' WITH NOFORMAT, NOINIT, NAME = N'hl7 db_SamirTesting_backup_20070310050809', SKIP, REWIND, NOUNLOAD, STATS = 10
" failed with the following error: "The statement BACKUP LOG is not allowed while the recovery model is SIMPLE. Use BACKUP DATABASE or change the recovery model using ALTER DATABASE.
BACKUP LOG is terminating abnormally.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

Command:BACKUP LOG [hl7 db_SamirTesting] TO DISK = N''D:mssqlackuphl7 db_SamirTestinghl7 db_SamirTesting_backup_200703100508.trn'' WITH NOFORMAT, NOINIT, NAME = N''hl7 db_SamirTesting_backup_20070310050809'', SKIP, REWIND, NOUNLOAD, STATS = 10
GO
BACKUP LOG [dg_efilm_153] TO DISK = N''D:mssqlackupdg_efilm_153dg_efilm_153_backup_200703100508.trn'' WITH NOFORMAT, NOINIT, NAME = N''dg_efilm_153_backup_20070310050809'', SKIP, REWIND, NOUNLOAD, STATS = 10
GO
BACKUP LOG [hl7 db] TO DISK = N''D:mssqlackuphl7 dbhl7 db_backup_200703100508.trn'' WITH NOFORMAT, NOINIT, NAME = N''hl7 db_backup_20070310050809'', SKIP, REWIND, NOUNLOAD, STATS = 10


Back Up Database (Transaction Log) (ICIS-SQL-SERVER)
Backup Database on Target server connection
Databases that have a compatibility level of 70 (SQL Server version 7.0) will be skipped.
Databases: All user databases
Type: Transaction Log
Append existing
Task start: 2007-03-10T05:08:09.
Task end: 2007-03-10T05:08:09.
Failed:(-1073548784) Executing the query "BACKUP LOG [dg_efilm_153] TO DISK = N'D:\mssql\backup\dg_efilm_153\dg_efilm_153_backup_200703100508.trn' WITH NOFORMAT, NOINIT, NAME = N'dg_efilm_153_backup_20070310050809', SKIP, REWIND, NOUNLOAD, STATS = 10
" failed with the following error: "The statement BACKUP LOG is not allowed while the recovery model is SIMPLE. Use BACKUP DATABASE or change the recovery model using ALTER DATABASE.
BACKUP LOG is terminating abnormally.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

Command:BACKUP LOG [hl7 db_SamirTesting] TO DISK = N''D:mssqlackuphl7 db_SamirTestinghl7 db_SamirTesting_backup_200703100508.trn'' WITH NOFORMAT, NOINIT, NAME = N''hl7 db_SamirTesting_backup_20070310050809'', SKIP, REWIND, NOUNLOAD, STATS = 10
GO
BACKUP LOG [dg_efilm_153] TO DISK = N''D:mssqlackupdg_efilm_153dg_efilm_153_backup_200703100508.trn'' WITH NOFORMAT, NOINIT, NAME = N''dg_efilm_153_backup_20070310050809'', SKIP, REWIND, NOUNLOAD, STATS = 10
GO
BACKUP LOG [hl7 db] TO DISK = N''D:mssqlackuphl7 dbhl7 db_backup_200703100508.trn'' WITH NOFORMAT, NOINIT, NAME = N''hl7 db_backup_20070310050809'', SKIP, REWIND, NOUNLOAD, STATS = 10


Back Up Database (Transaction Log) (ICIS-SQL-SERVER)
Backup Database on Target server connection
Databases that have a compatibility level of 70 (SQL Server version 7.0) will be skipped.
Databases: All user databases
Type: Transaction Log
Append existing
Task start: 2007-03-10T05:08:09.
Task end: 2007-03-10T05:08:09.
Failed:(-1073548784) Executing the query "BACKUP LOG [hl7 db] TO DISK = N'D:\mssql\backup\hl7 db\hl7 db_backup_200703100508.trn' WITH NOFORMAT, NOINIT, NAME = N'hl7 db_backup_20070310050809', SKIP, REWIND, NOUNLOAD, STATS = 10
" failed with the following error: "The statement BACKUP LOG is not allowed while the recovery model is SIMPLE. Use BACKUP DATABASE or change the recovery model using ALTER DATABASE.
BACKUP LOG is terminating abnormally.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

Command:BACKUP LOG [hl7 db_SamirTesting] TO DISK = N''D:mssqlackuphl7 db_SamirTestinghl7 db_SamirTesting_backup_200703100508.trn'' WITH NOFORMAT, NOINIT, NAME = N''hl7 db_SamirTesting_backup_20070310050809'', SKIP, REWIND, NOUNLOAD, STATS = 10
GO
BACKUP LOG [dg_efilm_153] TO DISK = N''D:mssqlackupdg_efilm_153dg_efilm_153_backup_200703100508.trn'' WITH NOFORMAT, NOINIT, NAME = N''dg_efilm_153_backup_20070310050809'', SKIP, REWIND, NOUNLOAD, STATS = 10
GO
BACKUP LOG [hl7 db] TO DISK = N''D:mssqlackuphl7 dbhl7 db_backup_200703100508.trn'' WITH NOFORMAT, NOINIT, NAME = N''hl7 db_backup_20070310050809'', SKIP, REWIND, NOUNLOAD, STATS = 10


Back Up Database (Transaction Log) (ICIS-SQL-SERVER)
Backup Database on Target server connection
Databases that have a compatibility level of 70 (SQL Server version 7.0) will be skipped.
Databases: All user databases
Type: Transaction Log
Append existing
Task start: 2007-03-10T05:08:08.
Task end: 2007-03-10T05:08:09.
Failed:(0) Database 'hl7 db_SamirTesting' will not be backed up because it does not have its recovery model set to Full or BulkLogged.

Back Up Database (Transaction Log) (ICIS-SQL-SERVER)
Backup Database on Target server connection
Databases that have a compatibility level of 70 (SQL Server version 7.0) will be skipped.
Databases: All user databases
Type: Transaction Log
Append existing
Task start: 2007-03-10T05:08:08.
Task end: 2007-03-10T05:08:09.
Failed:(0) Database 'dg_efilm_153' will not be backed up because it does not have its recovery model set to Full or BulkLogged.

Back Up Database (Transaction Log) (ICIS-SQL-SERVER)
Backup Database on Target server connection
Databases that have a compatibility level of 70 (SQL Server version 7.0) will be skipped.
Databases: All user databases
Type: Transaction Log
Append existing
Task start: 2007-03-10T05:08:08.
Task end: 2007-03-10T05:08:09.
Failed:(0) Database 'hl7 db' will not be backed up because it does not have its recovery model set to Full or BulkLogged.

Back Up Database (Full) (ICIS-SQL-SERVER)
Backup Database on Target server connection
Databases that have a compatibility level of 70 (SQL Server version 7.0) will be skipped.
Databases: All databases
Type: Full
Append existing
Task start: 2007-03-10T05:00:06.
Task end: 2007-03-10T05:08:08.
Success
Command:EXECUTE master.dbo.xp_create_subdir N''D:mssqlackupmaster''
GO
EXECUTE master.dbo.xp_create_subdir N''D:mssqlackupmodel''
GO
EXECUTE master.dbo.xp_create_subdir N''D:mssqlackupmsdb''
GO
EXECUTE master.dbo.xp_create_subdir N''D:mssqlackuphl7 db_SamirTesting''
GO
EXECUTE master.dbo.xp_create_subdir N''D:mssqlackupdg_efilm_153''
GO
EXECUTE master.dbo.xp_create_subdir N''D:mssqlackuphl7 db''
GO
BACKUP DATABASE [master] TO DISK = N''D:mssqlackupmastermaster_backup_200703100500.bak'' WITH NOFORMAT, NOINIT, NAME = N''master_backup_20070310050006'', SKIP, REWIND, NOUNLOAD, STATS = 10
GO
BACKUP DATABASE [model] TO DISK = N''D:mssqlackupmodelmodel_backup_200703100500.bak'' WITH NOFORMAT, NOINIT, NAME = N''model_backup_20070310050006'', SKIP, REWIND, NOUNLOAD, STATS = 10
GO
BACKUP DATABASE [msdb] TO DISK = N''D:mssqlackupmsdbmsdb_backup_200703100500.bak'' WITH NOFORMAT, NOINIT, NAME = N''msdb_backup_20070310050006'', SKIP, REWIND, NOUNLOAD, STATS = 10
GO
BACKUP DATABASE [hl7 db_SamirTesting] TO DISK = N''D:mssqlackuphl7 db_SamirTestinghl7 db_SamirTesting_backup_200703100500.bak'' WITH NOFORMAT, NOINIT, NAME = N''hl7 db_SamirTesting_backup_20070310050006'', SKIP, REWIND, NOUNLOAD, STATS = 10
GO
BACKUP DATABASE [dg_efilm_153] TO DISK = N''D:mssqlackupdg_efilm_153dg_efilm_153_backup_200703100500.bak'' WITH NOFORMAT, NOINIT, NAME = N''dg_efilm_153_backup_20070310050006'', SKIP, REWIND, NOUNLOAD, STATS = 10
GO
BACKUP DATABASE [hl7 db] TO DISK = N''D:mssqlackuphl7 dbhl7 db_backup_200703100500.bak'' WITH NOFORMAT, NOINIT, NAME = N''hl7 db_backup_20070310050006'', SKIP, REWIND, NOUNLOAD, STATS = 10


Please help,

-tim



View 3 Replies View Related

DB Engine :: Analyzing What Is Causing The Log File To Grow

Aug 20, 2015

For one of our database we have an issue where its log file got increased rapidly last week on Fri and Sat. The database is on SQL  server 2008 R2 with compatibility level at 80. Please see below log grow events :

First, we thought Index maintenance like Re-index and update stats could have been the reason, but when check the schedule that job ran on 16th using below code:

USE ABC
GO
EXEC sp_MSforeachtable @command1="print '?' DBCC DBREINDEX ('?', ' ', 80)"
GOEXEC sp_updatestatsGO

I know above is OLD fashioned, but we believe that should not be the major cause here? How can i determine what happened on 14th and 15th which cause the event to trigger and log file bumps to 80 and 70 GB both days.

View 8 Replies View Related

Changing To Simple Recovery Mode

Jun 26, 2002

Hi,

What is the impact of changing the recovery mode of a database from Full to simple? The client I am at has set their database to full recovery mode, set their log files to grow automatically. But I don't think they have ever done a backup of their transaction log (it has grown to over 19Gig, where the data portion of the database is only around 400M).

What is the impact of truncating the transaction log now? After truncating it, i would like to shrink the file to a managable number and change the recovery mode to simple (they don't need transaction log backups)

Any info on this would be appreciated.

Thanks in advance

Jim

View 1 Replies View Related

Db Backup Simple Vs. Full Recovery Mode

Feb 14, 2007

When we do a full database backup manually, we are seeing the trn file reflect the current date/time, but we are not seeing the mdf reflect the new date/time. And we are not seeing the transaction log file decrease in size. the recovery mode is set to full, do we need to change to simple to see both the mdf being backup'ed?

View 5 Replies View Related

Transaction Log Still Growing When In SIMPLE Recovery Mode

Dec 3, 2007

hi,
we have a SQL Server 2000 database which we set to 'SIMPLE' recovery mode at 6pm (due to nightly large data loads). We revert back to 'FULL' recovery mode at 6am.

My understanding was that in 'SIMPLE' recovery mode, the transaction log would not grow because it would automatically be truncated after a checkpoint. However this is not the case. I thought perhaps it could be due to a long running uncomitted transaction, but when I ran 'dbcc opentran', the oldest running transactions doesn't last for more than a couple minutes. I manually run a 'checkpoint' command as well in the hope of forcing the transaction log truncation. I repeat this a couple of times to no avail. When I run 'dbcc sqlperf(logspace)' , I can still see the transaction log growing.

It is not until I run 'backup log db with truncate_only' that the transaction log gets truncated.
I do not understand, why the transaction log does not get automatically truncated in SIMPLE recovery mode?

Andrew

View 11 Replies View Related

LOG Fills All Drive Space In Simple Recovery Mode

Dec 21, 2007



I am amazed to see this morning that log file consuming whole disk space even though the database is in simple recovery mode.

What could be the reasons to fill in the space even in simple recovery mode??

View 10 Replies View Related

SQL Tools :: In Simple Recovery Mode Can Do Live Differential Backup?

Jun 30, 2015

I have a small, ~10GB SQL 2008 R2 database, that was setup with simple recovery.  We do full backup each night at midnight when no one is using the database.  Is there any problems with doing differential backups during the day when users may be writing to the database?  Could I even do hourly differential backups while users are using the database?  I'm conflicted about switching over to full recovery mode and using transaction logs to have the ability restore data between backups.  If I can do a couple daily differential backups while users are using the database during the day, in addition to our nightly full backups,  than I  live with simple recovery mode.  

View 3 Replies View Related

Transact SQL :: Script To Set DB In Simple Recovery Mode And Visa-Versa

Jun 15, 2015

Wondering whether I can have following included in a script file:

1. set the current single user db from Full to Simple recovery mode.
2. Checkpoint and shrink the transaction log file (release all unused space)
3. set the current single user db from Simple recovery to Full recover mode.

View 7 Replies View Related

SQL Server Admin 2014 :: Unable To Shrink Log On Simple Recovery Mode Database

Jul 27, 2015

I have a database that I am trying to recover space from, it consists mostly of unallocated space, but I can’t seem to get that unused space released.

Database size: 40,245.13 MB
DatafileMB: 38,063.63, DataAvailableMB: 37,085.15
LogfileMB: 2181.51

Sysfiles shows:
fileidgroupidsizemaxsizegrowthstatusperfname
114872144-112820SomeDB
202792332684354561010486420SomeDB_log

The DB is in simple recovery mode. There are no open transactions (used dbcc opentran).

The server is running SQL Server 2014 and the DB is in compatibility mode SQL Server 2008 (100). It was upgraded to 2014 a month or two ago.

I have tried to re-size the log to 100mb, but any way I have tried (none gave errors), the log file remains the same size. I have tied to shrink the log file (through the UI and via DBCC commands) without success; no errors, but also no change in file size.

I have checked Log Reuse Waits, just in case, and as expected it showed “NOTHING” (select log_reuse_wait_desc, name from sys.databases)

I tried running a checkpoint, but that did not allow any resize or shrink to work.

I have tied creating large transactions to move the used point in the log file, in case this was the issue. I did this by creating tables that I drop after large inserts. While it shows me that the log space % used increased, the log file still does not allow the space to be reduced.

The following is what I was using for the transactions to get the log used.

BEGIN TRAN
select a.* into testtable from sysobjects a, sysobjects b, sysobjects c
ROLLBACK TRAN

Each insert creates 93,576,664 rows.

Running dbcc SQLPerf(logspace) :
DBLogSize(MB)LogSpaceUsed(%)Status
SomeDB2181.534.204890

Running dbcc loginfo:
RecoveryUnitIdFileIdFileSizeStartOffsetFSeqNoStatusParityCreateLSN
0211437342728192602640
02114373427211437424645701280

Do I just need to continue running large transactions until the log space used gets high enough to get the “end point” in the log to really move? Is there an easier way to accomplish this (I have several DBs that have the almost identical problem), what I am using moves the Log Space Percent Used about a percent on each execution.

View 9 Replies View Related

DB Engine :: Can Deleted Records Be Recovered In Simple Recovery Model?

Aug 21, 2015

Can the deleted records be recovered in Simple Recovery model database? Are the delete logs present there?

View 3 Replies View Related

Database In Simple Mode Yet Txn Log File Can Be Out Of Diskspace ?

Oct 10, 2005

Hi ,I have set up my database to be using "Simple" mode. This will not log anytxns ?I have got the err message saying the log file is full and i need to do atxn log backupi do not understand why , could anyone kindly advise ?tks & rdgs--Message posted via SQLMonster.comhttp://www.sqlmonster.com/Uwe/Forum...eneral/200510/1

View 1 Replies View Related

Backup Of Ldf File In Simple Recovery Model

Mar 20, 2008



Hello,



I have a question regarding the backup for the database in Simple Recovery Model.

In this Model, I know we can restore only to the last full backup or can use differential

Backup, if implemented as a part of backup.



But my point of confusion is about the backup of '.ldf' file, should those file should be backed up in the

Maintenance Plan, if yes does it help in reducing the size of Log file?

Do we need the backup of '.ldf' in phase of Restoring?



As I mention my database has Simple Recovery Model, but the size of log file is around 20GB,

Could not understand why as in this Model, normally it automatically truncate the Log file?



Help me to clear my these doubts,



thanks,




View 5 Replies View Related

Simple Recovery Model Database - Huge Log File

Nov 3, 2015

Have a database that's in "Simple" recovery mode whose .ldf has grown to 270GB.   This database is a data warehouse so "full" is not required.  I put it in simple mode a month ago and shrunk the log down and now it's filled up the disk. 

What steps can I take to mitigate this in future?  I've read that this is caused by long running transactions which fill the log for DR purposes.  Should I put the database back into full mode and backup/truncate daily.  

The auto-growth is set to 128MB which is very low. 

View 3 Replies View Related

Full Recovery Model - Log Doesn't Grow?

Feb 7, 2006

Hi all,I have a SQL Server 2000 database that is using the Full recoverymodel. The database is purely receiving inserts (and plenty of them)with maybe some view/table creation for reporting.In this state I would expect the log to grow ad infinitum but it getsto about 32% used and then empties.The log is not being backed up at all so am I missing something else?CheersDee

View 2 Replies View Related

SQL Server 2008 :: Log File Management In Simple Recovery Model

Sep 15, 2015

One of our database is in simple recovery model, and usually generating more than 220 GB log file (.ldf) every week. We are shrinking log file many times to release the space.

But as its not advisable I am looking for any other options. I suggested to change the recovery model to Full and start T-log backup, but client dont want to change recovery model.

Is there any way to manage Log file of Simple recovery model to maintain disk space?

Will full backup truncate log file ?

View 9 Replies View Related

LDF File Does Not Grow..

Jun 27, 2007

Bear with me - My SQL Server 2005 Maintenance is as good as a Newbie..

I was running a Very Large Transaction over the weekend (Say 10Mill Inserts)..
And after waiting for 3/4 Hrs for the transaction to complete -- Checked the LDF File, I has grown to a 100 GB.

After that i discovered that i had the Recovery Model as FULL .. So Killed the Job and Changed the recovery mode from Full -> Simple.

Now i see that the LDF file is not growing in size even though there are many transactions that were complete successfully (Still Very slow though)...

What am i missing here - Iam clueless as to why my LDF is not growing in size?

Any Ideas??

View 4 Replies View Related

SQL Recovery Mode

Aug 1, 2006

Hi,

How to make all MSSQL DBs run in Simple log form by default other than FULL so when we srhink DBs the logs will go bybye. :-)


Thanks

View 10 Replies View Related

Automatically Grow File

Jan 8, 2004

Hello everyone,
I have 45 GB db with
-Automatically grow file by 10 %
- full recovery
-log shipping every 5 minutes.
-full backup every 24 hrs

database grown from 33GB to 45 GB for 1 year period
4-5 times a year massive insert
done to database(no specific dates)

if I change autogrow to by 300MB or 4%

1.how would it affect insert process ?
2.how it affect daily performance ?

Thank you
Alex

View 3 Replies View Related

Automaticallly Grow File

Oct 1, 2004

What is the best option to set for File Growth?

Is it in megabytes or by percent?

View 3 Replies View Related

Sql 2005 Log File Grow Too Much

Oct 9, 2007



Hello,

I'm running a long and heavy query. during the running the log file of the DB is growing more than 20 GB and i'm running out of disk space consequently. Is there a way to restrict the log file size without demaging my query?

Thanks.

View 9 Replies View Related

Change Recovery Mode

Feb 19, 2008

We have 300+ databases on one sinlge server (SQL 2005). If I need to change recovery mode from full to simple for all of them, is there any way to do so? Please advice.

View 3 Replies View Related

Recovery :: How To Know If DB Is In Log-truncate Mode

May 5, 2015

I have a db running under simple recovery mode. I am really pressed at disk space, and we have a long running script that keeps failing with "no space left on the device" error. I noticed the log file is very large. I plan to set the max log file size but at the same time I want to know that the database is in the log-truncate mode - perhaps from the database itself. Is there any metadata that could tell me this?

View 7 Replies View Related

Can A Query Tell Us What Recovery Mode Is Being Used?

Oct 29, 2007

can t-sql be used to find out which recovery mode is on for a given db?

View 1 Replies View Related

My Log File Has Grow The Disk Full

Mar 20, 2004

My logfile has grow the disk full - the logfil is 25 gb and I have 4 gb free.

I can't shrink the log fil !

Can I set the log file to null ??

I have backup my datafil successfully!

Help!

View 9 Replies View Related

Database Recovery From Suspect Mode

Feb 26, 2002

Hi,

Could anyone please tell me steps to recover the database from the suspect
mode. The backup I got is very old. Can it be recovered without the backup.

Thanks in advance
John Jayaseelan

View 1 Replies View Related

Check Recovery Mode By Statement

Sep 14, 2006

hi...
is there a statement to display the what recovery model on the database instead using GUI. Thanks~~~

View 2 Replies View Related

Database Is In Bypass Recovery Mode

Sep 4, 2006

Hi all

My database 'a2rd' was marked as suspect
and i did the following steps to make it available

USE MASTER
select name, dbid, mode, status from sysdatabases where dbid =
db_id('a2rd')
UPDATE SYSDATABASES SET STATUS=-32768 WHERE NAME='a2rd'
EXEC sp_configure 'show advanced option', '1'
EXEC sp_configure 'allow updates', '1'
RECONFIGURE WITH OVERRIDE
DBCC NEWALLOC(a2rd)
DBCC TEXTALL (a2rd)
DBCC CHECKDB (A2RD


now how can i take the backup of the database that was in emergency mode..

Thanks in advance..

View 2 Replies View Related

Distribution Dtabase Recovery Mode.

Oct 26, 2007


By default, distribution database is set to simple recovery mode. Why ? Should this be changed to full ? how often should transaction logs be taken ? What is the recommendation ?

Thank you

View 1 Replies View Related

Auto Grow Enabled But DB Won't Grow

Jan 15, 2005

I've been through the forum and read a number of threads on people's DBs not growing and the answer usually is they don't have auotmatically grow data file. Unfortunately I have this on, but when I look at the properties of the database it reports the space available is 0.00 MB? Up until about two weeks ago I was showing appx 48% space utilization. When I ran an SP to show growth, it tells me that it was expanded by 20% yesterday, but SQL Server is still telling me the space available is zero.

The log file is also set for auto growth. The DB is 14.5 GB in size and the drives still have around 92 GB of space.

Has anyone experienced this before? Any ideas? Does anyone know of an SPs that can give me detailed info on internal data file size compared to stated size (i.e. wasted space in data file)? Is SQL Server doing something funny in the way it is seeing the database or data files individually? Any help is appreciated.

View 6 Replies View Related

Proactively Grow Data File Size

Jan 9, 2008

My primary (and only) data file has reached the point where it is auto growing. I would like to grow this file in one big chunk at an off peak time. I can't seem to find the code I need to make the file grow when I want it to?

View 1 Replies View Related







Copyrights 2005-15 www.BigResource.com, All rights reserved