 | |
Trimming HUGE Transaction Log
microsoft.public.sqlserver.tools microsoft.public.sqlserver.tools
 |
| | Thread Tools | Display Modes |
#1
 
| |||
| |||
|
Trimming HUGE Transaction Log -
10-13-2008
, 11:45 AM
#2
| |||
| |||
|
|
I've got an Access application with a SQL Server back end. SQL Server db is about 4 gig. Transaction log is about 10 gig. It just seems to keep growing. I' GUESSING Access never causes transactions to be committed, so the log file never drops those transactions. I tried something which SEEMS to work, but before I do this to production files - I'd like a little expert advice. -- I backed up the database -- I changed the recovery model to SIMPLE, -- I shurunk the log file to the minimum allowed (which was very small) -- I changed the recovery model back to FULL. If I do this after hours when everyone is gone, logging should begin before users every get back into the office. Does this seem like a plan?? -- Thanx in advance! Angelo |
#3
| |||
| |||
|
|
I've got an Access application with a SQL Server back end. SQL Server db is about 4 gig. Transaction log is about 10 gig. It just seems to keep growing. I' GUESSING Access never causes transactions to be committed, so the log file never drops those transactions. I tried something which SEEMS to work, but before I do this to production files - I'd like a little expert advice. -- I backed up the database -- I changed the recovery model to SIMPLE, -- I shurunk the log file to the minimum allowed (which was very small) -- I changed the recovery model back to FULL. If I do this after hours when everyone is gone, logging should begin before users every get back into the office. Does this seem like a plan?? -- Thanx in advance! Angelo |
#4
| |||
| |||
|
|
I've got an Access application with a SQL Server back end. SQL Server db is about 4 gig. Transaction log is about 10 gig. It just seems to keep growing. I' GUESSING Access never causes transactions to be committed, so the log file never drops those transactions. I tried something which SEEMS to work, but before I do this to production files - I'd like a little expert advice. -- I backed up the database -- I changed the recovery model to SIMPLE, -- I shurunk the log file to the minimum allowed (which was very small) -- I changed the recovery model back to FULL. If I do this after hours when everyone is gone, logging should begin before users every get back into the office. Does this seem like a plan?? -- Thanx in advance! Angelo |
#5
| |||
| |||
|
|
I've got an Access application with a SQL Server back end. SQL Server db is about 4 gig. Transaction log is about 10 gig. It just seems to keep growing. I' GUESSING Access never causes transactions to be committed, so the log file never drops those transactions. I tried something which SEEMS to work, but before I do this to production files - I'd like a little expert advice. -- I backed up the database -- I changed the recovery model to SIMPLE, -- I shurunk the log file to the minimum allowed (which was very small) -- I changed the recovery model back to FULL. If I do this after hours when everyone is gone, logging should begin before users every get back into the office. Does this seem like a plan?? -- Thanx in advance! Angelo |
#6
| |||
| |||
|
|
I've got an Access application with a SQL Server back end. SQL Server db is about 4 gig. Transaction log is about 10 gig. It just seems to keep growing. I' GUESSING Access never causes transactions to be committed, so the log file never drops those transactions. I tried something which SEEMS to work, but before I do this to production files - I'd like a little expert advice. -- I backed up the database -- I changed the recovery model to SIMPLE, -- I shurunk the log file to the minimum allowed (which was very small) -- I changed the recovery model back to FULL. If I do this after hours when everyone is gone, logging should begin before users every get back into the office. Does this seem like a plan?? -- Thanx in advance! Angelo |
#7
| |||
| |||
|
|
I've got an Access application with a SQL Server back end. SQL Server db is about 4 gig. Transaction log is about 10 gig. It just seems to keep growing. I' GUESSING Access never causes transactions to be committed, so the log file never drops those transactions. I tried something which SEEMS to work, but before I do this to production files - I'd like a little expert advice. -- I backed up the database -- I changed the recovery model to SIMPLE, -- I shurunk the log file to the minimum allowed (which was very small) -- I changed the recovery model back to FULL. If I do this after hours when everyone is gone, logging should begin before users every get back into the office. Does this seem like a plan?? -- Thanx in advance! Angelo |
#8
| |||
| |||
|
|
I've got an Access application with a SQL Server back end. SQL Server db is about 4 gig. Transaction log is about 10 gig. It just seems to keep growing. I' GUESSING Access never causes transactions to be committed, so the log file never drops those transactions. I tried something which SEEMS to work, but before I do this to production files - I'd like a little expert advice. -- I backed up the database -- I changed the recovery model to SIMPLE, -- I shurunk the log file to the minimum allowed (which was very small) -- I changed the recovery model back to FULL. If I do this after hours when everyone is gone, logging should begin before users every get back into the office. Does this seem like a plan?? -- Thanx in advance! Angelo |
#9
| |||
| |||
|
|
I've got an Access application with a SQL Server back end. SQL Server db is about 4 gig. Transaction log is about 10 gig. It just seems to keep growing. I' GUESSING Access never causes transactions to be committed, so the log file never drops those transactions. I tried something which SEEMS to work, but before I do this to production files - I'd like a little expert advice. -- I backed up the database -- I changed the recovery model to SIMPLE, -- I shurunk the log file to the minimum allowed (which was very small) -- I changed the recovery model back to FULL. If I do this after hours when everyone is gone, logging should begin before users every get back into the office. Does this seem like a plan?? -- Thanx in advance! Angelo |
#10
| |||
| |||
|
|
I've got an Access application with a SQL Server back end. SQL Server db is about 4 gig. Transaction log is about 10 gig. It just seems to keep growing. I' GUESSING Access never causes transactions to be committed, so the log file never drops those transactions. I tried something which SEEMS to work, but before I do this to production files - I'd like a little expert advice. -- I backed up the database -- I changed the recovery model to SIMPLE, -- I shurunk the log file to the minimum allowed (which was very small) -- I changed the recovery model back to FULL. If I do this after hours when everyone is gone, logging should begin before users every get back into the office. Does this seem like a plan?? -- Thanx in advance! Angelo |
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.