Viewing 15 posts - 34,966 through 34,980 (of 49,552 total)
You did notice that this thread is over a year old?
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 5, 2010 at 3:11 pm
That looks like a deadlock. It's possible you saw it in the transient state as it was getting identified, or one of the processes was already rolling back.
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 5, 2010 at 3:09 pm
joshua.aaanderson (1/5/2010)
what advice would you all have to not using cursors if youhave sensitive data that needs to be checked to maintain its integrity?
Write a set-based query. That'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
January 5, 2010 at 3:07 pm
Lynn Pettis (1/5/2010)
CirquedeSQLeil (1/5/2010)
Urgent, going to lose my job.http://www.sqlservercentral.com/Forums/Topic834653-338-1.aspx
And then three weeks later...
http://www.sqlservercentral.com/Forums/Topic842291-149-1.aspx?Update=1
Hmmm...I guess the prof gave him an extension?
Actually, nothing earlier indicated that it was urgent, so more like...
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 5, 2010 at 2:02 pm
Providing there was no switch to simple recovery between 5pm and the full backup at 11, yes.
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 5, 2010 at 1:57 pm
Yup. A second nonclustered index.
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 5, 2010 at 1:53 pm
John Rowan (1/5/2010)
This is a repost, please continue thread and responses here:http://www.sqlservercentral.com/Forums/Topic842291-149-1.aspx?Update=1
Actually, this is the original thread and the one you've linked is his 'now it's really urgent' repost.
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 5, 2010 at 1:50 pm
Jennifer Wang-317627 (1/5/2010)
Meanwhile, is there any way for me to limit one transaction to work on the table at one time? That would surely avoid the deadlocks.
An exclusive table...
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 5, 2010 at 1:48 pm
Actually, looking at it, I suggest a new nonclustered index.
Index key: SKU. Include column: Class.
The current index you have is not seekable for this query as Location isn't...
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 5, 2010 at 11:35 am
san43 (1/5/2010)
Why Class column? Its not used in the where clause right?
No, it's in the select. That's why I said add it as an INCLUDE column
I have to check...
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 5, 2010 at 11:32 am
altitude00 (1/5/2010)
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 5, 2010 at 10:55 am
Why no clustered index on that table?
Try adding Class as an include column for that nonclustered index. See if it helps.
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 5, 2010 at 10:54 am
If they don't have any indexes, then appropriate indexes would help. There's no minimum rows below which an index shouldn't be used. Test and see.
Have a look at this introductory...
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 5, 2010 at 10:53 am
Have you tested the statements separately? Have you used print to check the values of the date variable? Have you done selects to ensure that there really are (or are...
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 5, 2010 at 10:50 am
Looks ok. What exactly do you mean by 'It just doesn't seem to be working.'?
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 5, 2010 at 10:15 am
Viewing 15 posts - 34,966 through 34,980 (of 49,552 total)