Viewing 15 posts - 27,331 through 27,345 (of 49,552 total)
Are any rows returned by the following?
... WHERE Open = 'NULL'
... WHERE Open IS NULL
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
March 16, 2011 at 7:11 am
Blank and null are not the same.
Can you maybe attach a screenshot that shows the data?
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
March 16, 2011 at 6:43 am
Without knowing details it's hard to say.
Check the current behaviour. Is there significant blocking? Can the queries be optimised? Is there still significant blocking after doing so?
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
March 16, 2011 at 6:42 am
It might be in the default trace, I don't know if rename operations are caught there. If not and you had no custom traces running, there's no way to tell...
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
March 16, 2011 at 5:55 am
white shadow (3/16/2011)
Thinking it might lock the t-log file and put a hold on the script.
When the system-generated checkpoints run (in a system process) does that stop all operations in...
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
March 16, 2011 at 5:54 am
Grant Fritchey (3/16/2011)
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
March 16, 2011 at 5:50 am
white shadow (3/16/2011)
you could, but it would happen in another session, so it might make things worse.
???
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
March 16, 2011 at 5:49 am
aa.nichol (3/16/2011)
Would it be sensible to apply a job to issue a CHECKPOINT every so often?
Not in general. If you're doing a bulk operation, you may want to either add...
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
March 16, 2011 at 5:48 am
Please take a look through this http://www.sqlservercentral.com/articles/Transaction+Log/72488/
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
March 16, 2011 at 5:41 am
Please note: 2 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
March 16, 2011 at 4:50 am
Sometimes it's more efficient to break a query up and use temporary storage, like a temp table or, as you did, a table variable.
CTEs, despite their name, are not tables,...
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
March 16, 2011 at 1:58 am
For an OR you need one index for each part of the OR. A single composite index can't be used for seeks when there are ORs.
Try the following two indexes...
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
March 16, 2011 at 12:02 am
WayneS (3/15/2011)
Now I really want to see it! Good job on insulting any and all... sounds like Jeff and his pork chop launcher might be rubbing off on you!
That or...
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
March 15, 2011 at 11:59 pm
That's a memory-related error. It's saying that a page in memory has been changed when it should not. That's a nasty problem to have, hard to track.
It could be faulty...
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
March 15, 2011 at 11:59 pm
Steve Jones - SSC Editor (3/15/2011)
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
March 15, 2011 at 11:54 pm
Viewing 15 posts - 27,331 through 27,345 (of 49,552 total)