November 26, 2014 at 8:26 am
Hi folks,
is it important where i put a timestamp field in a row that gets used very often in a wide table? Is paging hurting me? :ermm:
Greetz
Query Shepherd
November 26, 2014 at 8:35 am
Order of columns doesn't matter in a 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
November 26, 2014 at 8:36 am
OK. Thanks Gail. And what about the explanation?
Greetz
Query Shepherd
November 26, 2014 at 8:54 am
How do you mean paging? Data is stored on pages. Do you mean page splits? Timestamp isn't going to lead to page splits unless you've indexed it and then it will only split the pages on the index, unless it's the cluster. I'm not sure what you're going for. Gail answered the first question.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
November 26, 2014 at 9:00 am
Query Shepherd (11/26/2014)
OK. Thanks Gail. And what about the explanation?
Errr... what explanation?
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
November 26, 2014 at 9:07 am
Yes. Sorry, I ment page splits and the timestamp is not indexed and the table is not a heap...
Greetz
Query Shepherd
November 26, 2014 at 10:30 am
Query Shepherd (11/26/2014)
Yes. Sorry, I ment page splits and the timestamp is not indexed and the table is not a heap...
Then it won't do anything any differently than any other fixed length data type.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply