homebrew01 (9/9/2013)

---

If it is inserting, and you want it to stop, I don't think you can avoid a rollback.

If you're lucky , it hasn't been doing inserts the entire 22...

Thanks.

That is what I did when I upgraded database...

I'm still having trouble shrinking the Transaction Log.

The Transaction Log was at 22 GB.

I backed up the Transaction Log and shrank the Log and it reduced the size to 9...

Steve Jones - SSC Editor (7/18/2013)

---

You may have the active portion of the log at the end of the file, which prevents it from shrinking. One of the things you...

Thanks for all of the replies.

I back up the transaction log hourly.

I use the WITH RECOVERY and WITH NORECOVERY quite a bit.

Recently I migrated just under 20 Databases from SQL Server 2005 and applied Full, differential and in some case Transaction...

Thank you for your advice.

I may eventually apply the restore to refresh the Development Environment.

But I'm not trying to restore at this point.

Thanks.

GilaMonster (7/15/2013)

---

Welsh Corgi (7/15/2013)

---

BACKUP LOG DataWarehouse TO DISK e= N'D:\Backup\TransactionLog\Data\DataWarehouse_backup_2013_07_15_181847_8601173.trn'

WITH NOFORMAT, NOINIT,

NAME = N'DataWarehouse_backup_2013_07_15_181847_8601173',

SKIP, REWIND, NOUNLOAD,...

BACKUP LOG [DataWarehouse] TO DISK = N'D:\Backup\TransactionLog\DataWarehouse\DataWarehouse_backup_2013_07_15_182558_8596801.trn' WITH NOFORMAT, NOINIT, NAME = N'DataWarehouse_backup_2013_07_15_182558_8596801', SKIP, REWIND, NOUNLOAD, NORECOVERY , COMPRESSION, STATS = 10

GO

declare @backupSetId as int

select @backupSetId...

BACKUP LOG DataWarehouse TO DISK e= N'D:\Backup\TransactionLog\Data\DataWarehouse_backup_2013_07_15_181847_8601173.trn' WITH NOFORMAT, NOINIT, NAME = N'DataWarehouse_backup_2013_07_15_181847_8601173', SKIP, REWIND, NOUNLOAD, NORECOVERY ,...

The transaction log for one of the Database was huge so the backup does not appear to working.

In the job history lists the job as successful and the backup file...

I ran the REBUILD on the Production Server and 26 Indexes are still 100% fragmented and 112 and above 80%.

Any ideas would be greatly appreciated.

After I ran the ALTER INDEX the Indexed Tables dropped below 1%.

Could it be the command is more effective or the I ran a REINDEX/REBUILD twice?

I was thinking of using Dave Pinal's script to rebuild the Indexes:

DECLARE @TableName VARCHAR(255)

DECLARE @sql NVARCHAR(500)

DECLARE @fillfactor INT

SET @fillfactor = 80

DECLARE TableCursor CURSOR FOR

SELECT OBJECT_SCHEMA_NAME([object_id])+'.'+name AS TableName

FROM sys.tables

OPEN TableCursor

FETCH NEXT...

For instance I have a job that basically stops loading records. If I kill it it messes up the data if I do not let it finish because of the...