Viewing 9 posts - 16 through 24 (of 24 total)
OK here it is .
This table had 35 Million Rows.
We were Updating the BitColumn Field.
There was also a Trigger which would write to another table, which is at...
June 13, 2011 at 10:51 am
Unfortunately I am not allowed to disclose more information as a Company Policy.
June 13, 2011 at 6:36 am
It is a simple UPDATE statement.
UPDATE <tablename> SET <columnName> = 1 WHERE <datefield> < 'TodaysDate'
And no the <ColumnName> is not part of any Index.
June 11, 2011 at 11:43 am
Thanks Gila
Was aware of CLR, was not aware of others. But the CLR was only taking up 8 KB.
Reduced the SQL Server Memory to 58 GB, just to be...
May 16, 2011 at 1:47 pm
Thanks Craig
I see people have already discussed this. Thanks for pointing this out to me.:-)
January 24, 2011 at 11:12 am
I see, I understand what you are saying now.
Then this begs the next question -- how do I know which NON_CLUSTERED index used this CLUSTERED index for "lookups"...
January 24, 2011 at 11:09 am
Oh wait a minute Gethyn -- are you trying to say that even though Lookups happen for NON CLUSTERED index -- it uses the CLUSTERED INDEX as a key for...
January 24, 2011 at 11:06 am
Ummm I don't think I have made myselves clear here.
All that you guys are pointing out to me is for a NON CLUSTERED index and I understand that, but then...
January 24, 2011 at 11:00 am
I understand what she says or so I think.
A lookup occurs when a nonclustered index was used to locate rows for a query, but the nonclustered index did not contain...
January 24, 2011 at 10:34 am
Viewing 9 posts - 16 through 24 (of 24 total)