Viewing 15 posts - 41,476 through 41,490 (of 49,562 total)
MarkusB (1/23/2009)
But I also noticed that this is a MYSQL procedure, not SQL Server. So you might better post it to a MySQL forum.
Good catch. I didn't even read the...
January 23, 2009 at 1:03 am
What you can do in VS is build that up as a string, assign it to a variable, do a debug.print (or equivalent) to get the string that will be...
January 23, 2009 at 12:54 am
I think I've found the major problem. You're missing brackets in the where clause. ANDs have precedence over ORs, so the way your where clause is written (with an or...
January 23, 2009 at 12:53 am
Jessica (1/22/2009)
I don't think I can upload the actual sqlplan file on here.
Zip it and attach it. If possible, for the actual exec plan, not the estimated.
The jpg doesn't have...
January 23, 2009 at 12:39 am
You say you're getting an error when calling that? What would the specific error message be?
January 23, 2009 at 12:30 am
It means you're calling a procedure, view or function from your procedure, and then from that proc calling another, etc 32 levels deep. Or it could be recursive with the...
January 23, 2009 at 12:29 am
madhu.arda (1/22/2009)
Is these dead locks are anyway related to having different collation settings.
Unlikely. Different collation would give you a collation mismatch error if there was a problem.
All I know about...
January 23, 2009 at 12:28 am
The_SQL_DBA (1/22/2009)
Paul, one question as a DBA what is the best way to avoid corruption in the first place..
I'm not Paul, but...
Ensure your IO subsystem is stable and performing...
January 22, 2009 at 2:26 pm
ashepard (1/22/2009)
Gail, do you have a good web rescource showing all the internal procecess that SQL 2005 or 2008 runs (log writer, dead lock detection, memory manager, etc)
I...
January 22, 2009 at 2:14 pm
Ummmm... forced parameterisation's not a band-aid. It can hurt more than help. It's used when you don't have access to the source code and hence can't change the queries in...
January 22, 2009 at 2:02 pm
PG (1/22/2009)
January 22, 2009 at 1:56 pm
DBADave (1/22/2009)
although who is to say the author is correct.
Connor's currently the program manager of the Query Optimisation team and, previously (iirc) was one of the lead developers...
January 22, 2009 at 1:35 pm
Network admins at my previous company didn't allow any of those to be used anywhere.
January 22, 2009 at 1:30 pm
You can always combine include columns without an effect
You can usually combine the inequalities without breaking anything, not always
You usually can't combine equality columns without causing a problem.
I blogged earlier...
January 22, 2009 at 1:29 pm
tgarland (1/22/2009)
I have thought about combining those into one index that looks like the following but I am not sure if that would make the index less valuable:
Looks fine.
This...
January 22, 2009 at 1:09 pm
Viewing 15 posts - 41,476 through 41,490 (of 49,562 total)