Viewing 15 posts - 46 through 60 (of 84 total)
Hi,
I agree with all the above answers, especially Gails.
It is a misconception that constraints always hurt performance. Maybe it was so a long time ago. Constraints can actually be used...
December 3, 2010 at 11:58 am
Grant, thank you very much!
Regards
Istvan Kathi
December 1, 2010 at 11:13 am
Hi,
I have found an interesting discussion about the same topic: LIKE vs Equals
I would also recommend the following blog: SQL in the Wild[/url]. There seems to be a lot about...
December 1, 2010 at 3:38 am
Yes I agree with you, apparently the optimizer treats the "LIKE" and "=" variants differently, although in this case they are same and are interchangeable.
I was hoping that there is...
November 30, 2010 at 10:10 am
You have a SELECT *
Do you really need all the columns returned? You have a RID lookup on the heap because there is no clustered index on the table. Good...
November 30, 2010 at 8:42 am
Hi,
How many rows are there in the table?
Could you post the execution plans also (not the pictures)?
Regards
November 30, 2010 at 5:02 am
Hi,
Interesting, so far one observation:
There don't seem to be any clustered index on the table. Is this table created only for experiment?
How is the "specialindex" created? Source would be nice.
Does...
November 30, 2010 at 4:09 am
Hi,
I would like to have more information about the system queried.
* Does the report data comes from one single database or several?
* If several databases, are they within the same...
November 30, 2010 at 3:38 am
GilaMonster (11/30/2010)
It depends on the execution plan that the optimiser picks.
Hi Gail. Could you explain it a little more detailed for this particular case? That would be interesting.
Thanks
Istvan Kathi
November 30, 2010 at 3:34 am
Hi,
As a column is parameter to the function, there is logically no other way, but to execute it for all rows. No intelligence in the optimizer, in my opinion, can...
November 30, 2010 at 2:56 am
There might be setting in the driver that aborts the way your app team request, but that shouldn't be the connection timeout. It seems logical to me that such abortion...
November 26, 2010 at 7:27 am
Hi,
I am not completely sure, but I think that the timeout in the client should mean the wait time for the database server to respond to the query. If the...
November 26, 2010 at 5:38 am
A first quick look on the query plan provided shows that you have two heavy sort operations on:
[StudentTest].[dbo].[StudentHistory].StudentId Ascending,
[StudentTest].[dbo].[StudentHistory].StudentHistoryId Descending
These take 48% of the resource. You should have an...
November 26, 2010 at 5:27 am
Yes, it looks like you are using SQL Server 2005, so you are stuck with either datetime and smalldatetime. Which one to choose depends on the range and precision required....
November 25, 2010 at 5:53 am
Viewing 15 posts - 46 through 60 (of 84 total)