Tag Info

New answers tagged

0

in order to release the space you first need to change the recovery model from full to simple, then you can release the space as you have mentioned.After it is finished you can revert from simple to full anyway this is a temporary fix.. the log will eventually grow again sooner or later..


4

I could not put this as comment so here it is for you. It is not compete answer to your question because your question can either be correctly answered by person working in Microsoft or Paul Randal(I guess). All I can say for all paractical purposes every information is logged. You can read the contents of log file using undocumented command select * from ...


0

When testing my backup plan on a VM test server which was disconnected from the network I was running a backup and then used the shrink command only. I use a SIMPLE recover model, still I had to force the setting of the database to SIMPLE mode, only then I could shrink my t-logs. The conclusion seems that if you have a database in SIMPLE recover model, not ...


1

My question is ,is there a way to read logrecord output of fn_dblog(null,null) from sql Reading transaction log using fn_dblog is not supported by Microsoft. So you should avoid running this command on production server. You can run this on UAT/Test environment. What do you exactly want to read from output of fn_dblog, can you be precise. There are ...


0

I'm an open sorcerer and cannot afford the license fees for Change Data Capture, it's only available with Microsoft SQL Server Enterprise Edition. So I've implemented change tracking with SQL triggers. The trigger adds an entry into the audit table, which contains among other things the before and after image of the data as XML, more details can be found ...


1

I finally found the answer Red gate transaction log management book by Tony and Gail shaw. Below is the Snip for a select into operation done in full recovery model: From the above snip we can see all the operations done to sometable are logged under the context of lop_format_page and logrecordlength is also 8276 bytes which indicates SQl eventhough ...


0

The reason your logs are filling up is due to the Index maintenance, not the backups. Kin alluded to this and suggested you take those index maintenance routines out of the maintenance plans. However, this will not stop the logs from filling up during index maintenance. Solutions like Ola Halengren's maintenance scripts will provide some logic around ...


5

What I am trying to understand is why this is occurring, and how to prevent it. Maintenance Plans do not have much logic that you can implement when dealing with index fragmentation and once you configure it, they run regardless if you really need a reorg or rebuild on your indexes. You are better off implementing Ola's backup solution as well as ...


2

Whoever told you "When rolling forward to end of logs without specifying overflow log path only active logs will be read" was wrong. When you have LOGARCHMETH1 set to DISK, TSM, USEREXIT or VENDOR, the DB2 log manager EDU (db2logmgr) is responsible for moving log files to and from the archive location. When performing a ROLLFORWARD operation, DB2 will ...


3

Numeric(9, 10) is not a valid data type specification. The scale must be less than or equal to the precision. I'll assume the actual column has a smaller scale specification. When you change a column from a precision of 1-9 to one of 10-19, the storage size increases from 5 to 9 bytes. This is a fully logged operation regardless of your recovery model ...



Top 50 recent answers are included