Viewing 15 posts - 91 through 105 (of 529 total)
Hello,
I do not have very much experience with indexed views but the problem I belive has affected me most are that my SET options differ from the SET options that...
September 28, 2006 at 8:57 am
Okay, say more then 1000 rows. Say an OLAP user want's extract data from the datawarehouse with adhoc statements. Say in this case you need 2.000.000 rows traveling over the wire,...
September 28, 2006 at 8:41 am
Hello!
Just a quick question. Have you considered partitioning? If your data amout is huge maybe partitioning can offset the extra cost of a complicated query plan? And you could 'drop'...
September 19, 2006 at 1:52 am
Well, I agree that there are no X table locks being put on system tables in any case of BEGIN TRAN ; SELECT ... INTO ... since I did actually explicitly...
September 18, 2006 at 6:15 am
It would seem that the KB that Jim posted describes exactly this error message you now are seeing.
Did your problem get solved?
September 17, 2006 at 7:58 am
Thanks, I didn´t know about this potential pitfall when using SQL Server 2005 64bit and linked servers..
September 17, 2006 at 7:55 am
If you ask yourself that question then you haven´t met many developers... And it is still true that SELECT/INTO creates eXclusive locks, try sp_lock and see for yourself. It places...
September 17, 2006 at 7:50 am
P.S Even when creating temporary tables you lock the system tables. I.e. even though your table isn't visible to anyone else you still create concurrency issues.
Hanslindgren
September 15, 2006 at 8:23 am
I would say never
Consider this, what happens when you create a table? The best outcome is that SQL Server just places eXclusive...
September 15, 2006 at 8:20 am
...and SELECT ... INTO ... should never be used, for major concurrency issues, if you are not using TOP 0.
September 15, 2006 at 3:27 am
Note: Be careful when you are using VARCHAR without specifying a length. BOL states that when casting/converting VARCHAR, without a length, defaults to length=30. When declaring a variable of VARCHAR...
September 15, 2006 at 3:17 am
Check the SET settings that you connections are using, they have to be the same for SQL Server to reuse the execution plan. This is probably why your SP takes...
September 15, 2006 at 2:59 am
What do you mean by 'kicking users out'? Are they getting errors that terminates the connections? What kind of errors are they getting?
Are they maybe getting timeouts? Try to increase...
September 15, 2006 at 2:51 am
To find out the most timeconsuming queries you can setup a trace, save to a table and then do a SELECT from the trace table ORDER BY duration DESC.
Do you have...
September 15, 2006 at 2:48 am
As far as I know there should be no problems linking a 64Bit 2k5 with a 2k.
Have you checked if the named pipes protocol has been disabled on the 2k machine?
September 15, 2006 at 1:10 am
Viewing 15 posts - 91 through 105 (of 529 total)