Viewing 15 posts - 20,746 through 20,760 (of 49,552 total)
You mean like option 4?
123456789012345678901234567890 and 123456789012345678901234567890
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
January 26, 2012 at 7:15 am
The error implies there were. Did you check MSDB backup tables? Did you check the LSNs in the full and diff backup headers?
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
January 26, 2012 at 7:14 am
Are you absolutely sure that the differential you have is based off the full backup that you restored? There were no other full backups taken between the time that full...
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
January 26, 2012 at 6:53 am
Try taking the backup WITH CHECKSUM, it could be getting damaged during backup, after backup when it's copied. Could also be the destination server is mangling the data during/after restore.
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
January 26, 2012 at 6:39 am
Please post table definitions, index definitions and execution plan, as per http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
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
January 26, 2012 at 6:02 am
You have a condition after the ELSE. ELSE statements don't take conditions. The syntax is
IF <condition>
<statement block>
ELSE
<statement block>
If you need to test one set of conditions then another...
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
January 26, 2012 at 5:59 am
That's your own connection. You're blocking the restore with your own session, make sure you're connected to a database other than the one you are restoring over.
p.s. Please don't type...
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
January 26, 2012 at 3:34 am
Your system resource database is damaged. Get out the backup of the files of that DB (since it can't be backed up normally only file-level backups are possible) and replace...
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
January 26, 2012 at 3:31 am
A deadlock quite simply is when two or more processes are waiting for locks that the other processes have. None can continue until the locks are released, none will release...
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
January 26, 2012 at 2:19 am
Ask your DBA to run an integrity check on whatever database you are connecting to and see if there's any corruption
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
January 26, 2012 at 2:18 am
SQL Kiwi (1/25/2012)
Backwards compatibility has a lot to answer for. I cringe slightly every time I see a variable-length data type used without an explicit maximum length value.
Only slightly?
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
January 26, 2012 at 1:40 am
hkflight (1/25/2012)
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
January 26, 2012 at 1:39 am
p.s. 3 year old thread.
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
January 26, 2012 at 1:37 am
Normal behaviour. SQL will generally use memory up to the amount on the server or max server memory (which by default is 2 TB).
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
January 25, 2012 at 3:55 pm
Edit: Nevermind...
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
January 25, 2012 at 3:41 pm
Viewing 15 posts - 20,746 through 20,760 (of 49,552 total)