Viewing 15 posts - 10,906 through 10,920 (of 49,552 total)
Koen Verbeeck (11/18/2013)
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
November 18, 2013 at 1:02 am
Koen Verbeeck (11/17/2013)
Wouldn't a compressed full backup/restore have been faster?
A normal uncompressed backup/restore would likely have been faster and less prone to random failures.
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
November 18, 2013 at 12:44 am
I disagree with you completely.
Every table should have a clustered index, but certainly not on 'a random column'. The column has to be carefully chosen. That's irrelevant to this question...
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
November 18, 2013 at 12:41 am
None, there's no index useful for that query.
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
November 18, 2013 at 12:21 am
Restore then, run a checkDB with data_purity, update all stats with fullscan, run DBCC updateusage. Then consider whether you're going to change the compatibility level
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
November 17, 2013 at 11:54 pm
Maybe. But it's a temporary mitigation. If you have stuff fragmenting MemToLeave, increasing the size will delay the problems, not prevent them.
Also, that means that, without AWE or 3GB, you...
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
November 17, 2013 at 10:16 pm
Post the plan.
Not seeing why you're concerned though. Convert implicit isn't expensive, it just prevents index seeks, and cast does exactly the same.
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
November 17, 2013 at 10:11 pm
Oracle_91 (11/17/2013)
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
November 17, 2013 at 10:06 am
1) you can, but you should probably figure out what it's doing first and what will happen when it gets undone.
2) Until the rollback completes. Do not restart SQL unless...
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
November 17, 2013 at 2:03 am
The error is because two files were specificed for the backup. This is commonly by mistake, where there were two files listed in the destination box on the backup dialog...
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
November 16, 2013 at 8:13 am
No guarantee of any order. I think with the open table you can click a button at the top to get the query, add the order by and re-run, but...
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
November 16, 2013 at 2:31 am
A restore recreates the database exactly as it was at the time of backup, including all file sizes. You need the same space for the files as the source database...
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
November 15, 2013 at 6:59 am
Unless you're talking about many minutes of processing time and GB of TempDB space, just let the temp tables go out of scope and they'll be automatically dropped.
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
November 15, 2013 at 6:32 am
If you need to empty the table it's fine, faster than delete. If you don't have further use for the table, drop it.
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
November 15, 2013 at 6:05 am
ganeshc27 (11/15/2013)
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
November 15, 2013 at 5:54 am
Viewing 15 posts - 10,906 through 10,920 (of 49,552 total)