Viewing 15 posts - 7,081 through 7,095 (of 49,552 total)
NO!
If you mean a file backup of the log, that will trash your database. DO NOT ever restore database files from a file backup unless you know exactly what you're...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
December 4, 2014 at 9:17 am
Well that would explain why the log isn't growing.
Looks like problems with drive or file system. Got a system admin there?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
December 4, 2014 at 9:06 am
So you have an open transaction that's preventing log reuse. Could be that the autogrow increments are too small and the log isn't growing fast enough. Could be that the...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
December 4, 2014 at 8:42 am
Can you post the exact error you're getting?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
December 4, 2014 at 8:32 am
Stop shrinking your log file!
You're just wasting resources, both in the shrink and when the file regrows (which it will have to do), as well as slowing your app down...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
December 4, 2014 at 8:07 am
Igor Micev (12/4/2014)
Could be IO Completion due to indexes reorganize and stats updates?
IO Completion I think is autogrows, but not sure. It's not normal page reads.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
December 4, 2014 at 4:49 am
Either you've also got transactional replication that's not running, or the CDC jobs are not all running properly. Only two ways you'll have long-lasting REPLICATION log reuse waits and a...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
December 4, 2014 at 4:48 am
Please post the involved queries and the deadlock graph
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
December 4, 2014 at 4:47 am
lilywhites (12/4/2014)
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
December 4, 2014 at 4:46 am
charipg (12/4/2014)
But some CDC jobs are setup , is this the issue ?
If they're not running, yes.
Do note, by running the repldone commands, you're invalidated the CDC stuff and lost...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
December 4, 2014 at 3:05 am
charipg (12/4/2014)
"Server was unable to process request. ---> The transaction log for database 'xxxx' is full due to 'REPLICATION'."
You have a transactional replication publication? Is the log reader agent not...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
December 4, 2014 at 2:33 am
Serlal (12/4/2014)
I think being in Full Recovery Mode and Not Taking Log Backups can be the reason for this.
No, it can not. Full recovery model and no log backups results...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
December 4, 2014 at 2:32 am
Page latch, don't know, would need to see the exact resource.
The latch wait is related to parallel table scans. Tune your queries to avoid large table scans running in parallel
ASYNC_NETWORK_IO...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
December 4, 2014 at 1:55 am
Partitioning is not a query optimisation technique. It's for data management. If you're trying to make queries faster, stop looking at partitioning.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
December 4, 2014 at 1:48 am
https://www.simple-talk.com/sql/backup-and-recovery/the-sql-server-instance-that-will-not-start/
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
December 4, 2014 at 1:46 am
Viewing 15 posts - 7,081 through 7,095 (of 49,552 total)