Viewing 15 posts - 23,866 through 23,880 (of 49,552 total)
SQLkiwi (8/26/2011)
GilaMonster (8/26/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
August 26, 2011 at 11:27 am
Grant Fritchey (8/26/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
August 26, 2011 at 11:26 am
btw, one way this can easily happen (thought of earlier, but didn't mention as it requires someone to have done silly things to the table)
CREATE TABLE ThisIsAHeap (
Column1 INT...
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
August 26, 2011 at 11:22 am
SQLkiwi (8/26/2011)
GilaMonster (8/26/2011)
Can anyone possibly see how an update WHERE <identity column> = <constant value> could possibly update the entire table?http://www.sqlservercentral.com/Forums/Topic1166215-1292-1.aspx
Without clicking the link (I should know better!) one way...
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
August 26, 2011 at 11:18 am
SQLRNNR (8/26/2011)
Brandie Tarvin (8/26/2011)
GilaMonster (8/26/2011)
Can anyone possibly see how an update WHERE <identity column> = <constant value> could possibly update the entire table?http://www.sqlservercentral.com/Forums/Topic1166215-1292-1.aspx
I put in my 2 cents, but Jeff...
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
August 26, 2011 at 11:13 am
Brandie Tarvin (8/26/2011)
GilaMonster (8/26/2011)
Can anyone possibly see how an update WHERE <identity column> = <constant value> could possibly update the entire table?http://www.sqlservercentral.com/Forums/Topic1166215-1292-1.aspx
I put in my 2 cents, but Jeff seems...
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
August 26, 2011 at 10:59 am
Can anyone possibly see how an update WHERE <identity column> = <constant value> could possibly update the entire table?
http://www.sqlservercentral.com/Forums/Topic1166215-1292-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
August 26, 2011 at 10:53 am
Cool, now the table and index definitions please? And maybe the query that you were running?
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
August 26, 2011 at 10:27 am
No. You want such a role, you'll have to create it yourself.
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
August 26, 2011 at 10:25 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
August 26, 2011 at 10:19 am
Didn't ask for a word doc with a picture of the exec plan. Please post the actual execution plan. See the article I previously referred you to.
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
August 26, 2011 at 10:19 am
Rich Yarger (8/26/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
August 26, 2011 at 10:16 am
Rich Yarger (8/26/2011)
That's what I thought, but that was not what ended up happening.🙁
You either didn't select the where clause when you ran the update (quite common) or every row...
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
August 26, 2011 at 10:11 am
CREATE TABLE ThisIsAHeap (
Column1 INT IDENTITY,
ColumnA CHAR(1),
ColumnB CHAR(1)
)
-- 505 rows
INSERT INTO ThisIsAHeap (ColumnA, ColumnB)
SELECT LEFT(NAME,1), RIGHT(NAME,1) FROM sys.columns AS c
UPDATE [dbo].ThisIsAHeap
SET ColumnA = 'X', ColumnB = 'Y'
WHERE...
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
August 26, 2011 at 10:10 am
Didn't highlight the where clause?
Doesn't matter what the structure is, if run in its entirety, that will update the rows where Column1 = 123, only
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
August 26, 2011 at 10:07 am
Viewing 15 posts - 23,866 through 23,880 (of 49,552 total)