Viewing 15 posts - 34,981 through 34,995 (of 49,552 total)
iqtedar (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:14 am
It's not. The select has S and IS locks. Look at the owner list for which locks which process has and wants. The select has a page lock in mode...
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:10 am
Technically those two indexes are not duplicates. One enforces the primary key, one allows filter on two columns. Unless you have a good reason, I'd actually leave them.
Widening the pk...
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 8:31 am
jason.stephens (1/5/2010)
I guess my only question is when should I start worrying about non-leaf nodes for fragmentation? How big does it have to be?
Rough guess, same place as the leaf...
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 8:06 am
pankaj.baluni (1/5/2010)
if not then I'm sorry to say that the DB is gone now.....
That is not necessarily true. There are ways to repair a SQL database with varying amounts of...
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 8:02 am
Please post SQL 2000 questions in the SQL 2000 forums in the future.
Please post table definitions, sample data and desired output. Read this to see the best way to post...
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 7:21 am
Please don't cross post. It just wastes peoples time and fragments replies.
No more replies to this thread please. Direct replies to: http://www.sqlservercentral.com/Forums/Topic841706-150-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
January 5, 2010 at 7:20 am
If detailed has to be used, stick a where clause and filter for index level = 0
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 7:18 am
Jack Corbett (1/5/2010)
Another option is to group by the common columns and take max(avg_fragmentation_in_percent)
I wouldn't suggest that. Consider the case of an index with a 5-page intermediate level that's 80%...
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 6:57 am
In detailed mode there's a row for each level of the index. In limited there's only a row for the leaf level (level 0).
Since the intermediate levels are much smaller...
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 6:52 am
Well, you can't rebuild a heap, so fragmentation levels for that (which, btw are extent fragmentation not logical fragmentation) won't change with an index rebuild.
If you've got an average page...
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 6:48 am
Don't try to migrate the system tables. Not recommended, not a good idea.
If you're doing an in-place upgrade, the installer will take care of that. If you're doing another...
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 6:02 am
You may be able to remove both subqueries and just have one query with an OR in the join clause. (INNER JOIN <second table> ON <condition> OR <condition>). It'll look...
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 6:00 am
Grant Fritchey (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 5:54 am
Are you returning different rows from the tables in each part? If so, it may be the easiest way of doing this.
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 5:49 am
Viewing 15 posts - 34,981 through 34,995 (of 49,552 total)