Viewing 15 posts - 17,386 through 17,400 (of 49,552 total)
Golfer22 (7/26/2012)
Could temporary tables help? Or table-valued variables?
If the query is relatively simple (small number of tables), probably not.
If you post the query, it would help.
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
July 27, 2012 at 12:26 am
dan-572483 (7/26/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
July 26, 2012 at 2:47 pm
Well, considering that I've seen and heard claims from MS that it's perfect and all you'll ever need for tuning and makes coffee too....
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
July 26, 2012 at 2:42 pm
kevinsql7 (7/26/2012)
Msg 155, Level 15, State 1, Line 1'TRUNCATE_ONLY' is not a recognized BACKUP option.
What is the new option in SQL Server 2008?
Simple recovery model.
Please read through this - Managing...
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
July 26, 2012 at 12:41 pm
And the vague question of the week award goes to: http://www.sqlservercentral.com/Forums/Topic1336028-391-1.aspx
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
July 26, 2012 at 11:45 am
You're IO bound. Fiddling with CPU and memory won't help, the IO subsystem is the bottleneck.
Can you write the backups to a different destination? One that's faster preferably.
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
July 26, 2012 at 10:06 am
Yup.
You can drop the index only on RecordType. The chances of that slowing any queries down as a result are incredibly slim.
Do test this before doing it in production. If...
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
July 26, 2012 at 7:12 am
Because someone turned AWE off.
The only way that a 32 bit instance could use 28GB of memory is if it had AWE enabled. So if it was using 28...
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
July 26, 2012 at 6:45 am
jitendra.padhiyar (7/26/2012)
Restore is possible if I have single or couple of db, but if I have many db than its not possible to restore each db and test.
Why 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
July 26, 2012 at 6:42 am
You run checkDB to see if you have corruption, not when you have corruption.
All databases should get regular scheduled integrity checks.
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
July 26, 2012 at 6:41 am
All databases should have regular integrity checks run on them.
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
July 26, 2012 at 6:08 am
Golfer22 (7/25/2012)
How do you know when a query cannot be further optimized?
That's very hard. When you can find no way to improve it, then you could say that, but it's...
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
July 26, 2012 at 6:07 am
subbareddy542 (7/26/2012)
and also use with(nolock) option in that query.
Recommending a bad idea with no discussion of the side effects?
See - http://blogs.msdn.com/b/davidlean/archive/2009/04/06/sql-server-nolock-hint-other-poor-ideas.aspx
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
July 26, 2012 at 5:55 am
jitendra.padhiyar (7/26/2012)
Is RESTORE ONLY and With CHECKSUM are 100% sure to validate backup files ?
No, I said above that it is not. It's very close, but it's not a 100%...
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
July 26, 2012 at 5:50 am
RESTORE VERIFYONLY if you took the backup WITH CHECKSUM. Even that's not a 100% guarantee. Best thing is to restore 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
July 26, 2012 at 3:08 am
Viewing 15 posts - 17,386 through 17,400 (of 49,552 total)