|
|
|
#1 |
|
Messages: n/a
Hébergeur: |
When I run a SPROC I get the following error:
Msg 9002, Level 17, State 1, Procedure nepBuildArchticsTableCopies, Line 82 The transaction log for database DB_Name' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases Does anyone know what this means and how I can fi this problem? Thank you!!!!!!!!!!!!!!!!! R |
|
|
|
#2 |
|
Messages: n/a
Hébergeur: |
bcap
Your log file is full as per error message. See on the disk, do you have a free space at all? What is recovery model you set up to the LOG? Is it full or simple? "bcap" <rayh@patriots.com> wrote in message news:8b416985-7d7f-405a-b450-06af1dcfcc09@27g2000hsf.googlegroups.com... > When I run a SPROC I get the following error: > > Msg 9002, Level 17, State 1, Procedure nepBuildArchticsTableCopies, > Line 82 > The transaction log for database DB_Name' is full. To find out why > space in the log cannot be reused, see the log_reuse_wait_desc column > in sys.databases > > > Does anyone know what this means and how I can fi this problem? > > Thank you!!!!!!!!!!!!!!!!! > > R |
|
|
|
#3 |
|
Messages: n/a
Hébergeur: |
Hi Uri,
Thank you for your response. I am hardly a DBA, can you tell me where to go to check if it is full or simple? Thanks again! |
|
|
|
#4 |
|
Messages: n/a
Hébergeur: |
bcap
SS2000 select name,convert(varchar(50), DatabasePropertyEx(name,'Recovery')) from master..sysdatabases SS2005 SELECT name,recovery_model_desc FROM sys.databases "bcap" <rayh@patriots.com> wrote in message news:f35632f6-b552-4243-9664-81651b32b0c4@c58g2000hsc.googlegroups.com... > Hi Uri, > > Thank you for your response. I am hardly a DBA, can you tell me where > to go to check if it is full or simple? > > Thanks again! |
|
|
|
#5 |
|
Messages: n/a
Hébergeur: |
Thank you! I am current set to FULL!
|
|
|
|
#6 |
|
Messages: n/a
Hébergeur: |
"bcap" <rayh@patriots.com> wrote in message
news:bcb5df8e-3877-41d1-af51-f18e001b9f43@i76g2000hsf.googlegroups.com... > Thank you! I am current set to FULL! You'll want to change it to simple mode. If not you'll keep running out of space; UNLESS you do a full database backup regularly - which will free space in the database files. |
|
|
|
#7 |
|
Messages: n/a
Hébergeur: |
It seems that the problem is about the Log file.
Taking Full Backups would not empty the Log file, he needs to take Log Backup for this purpose. -- Ekrem Önsoy "Ian Boyd" <ian.msnews010@avatopia.com> wrote in message news:OBE3Jt25IHA.3696@TK2MSFTNGP04.phx.gbl... > "bcap" <rayh@patriots.com> wrote in message > news:bcb5df8e-3877-41d1-af51-f18e001b9f43@i76g2000hsf.googlegroups.com... >> Thank you! I am current set to FULL! > > You'll want to change it to simple mode. > > If not you'll keep running out of space; UNLESS you do a full database > backup regularly - which will free space in the database files. > |
|
|
|
#8 |
|
Messages: n/a
Hébergeur: |
you can see the log_reuse_wait_desc in sys.databases system view. It shows
you some factors that can delay log transaction reuse. For some reason, displayed by log_reuse_wait_desc, your log file could not get more transactions added to. "bcap" wrote: > When I run a SPROC I get the following error: > > Msg 9002, Level 17, State 1, Procedure nepBuildArchticsTableCopies, > Line 82 > The transaction log for database DB_Name' is full. To find out why > space in the log cannot be reused, see the log_reuse_wait_desc column > in sys.databases > > > Does anyone know what this means and how I can fi this problem? > > Thank you!!!!!!!!!!!!!!!!! > > R > |
|
![]() |
| Outils de la discussion | |
|
|