Viewing 15 posts - 45,481 through 45,495 (of 49,571 total)
Just beware of parameter sniffing. Taht format of where clause tends to have very bad plan reuse and intermittent bad performance.
For structures like that, WITH RECOMPILE may be necessary.
July 24, 2008 at 7:55 am
angie stein (7/24/2008)
Brandie Tarvin (7/24/2008)
Does this technobabble make sense?Ok, so it sounds like you should usually restrict the growth (esp. in prod), unless there's a good reason to do otherwise.
In...
July 24, 2008 at 7:53 am
Brandie Tarvin (7/24/2008)
Sheer laziness or the inability to properly determine the growth rate of your DB. @=)
Intersting opinion. 😉
My main system is more a datawarehouse than anything. It grows...
July 24, 2008 at 7:48 am
Brandie Tarvin (7/24/2008)
I'd really love to have enough partitions in my SAN to have more than one file for my TempDB. @sigh. Gail, you're making me jealous. @=)
They're...
July 24, 2008 at 7:40 am
That's still a row-by-row scenario. Look at Jeffrey's suggestion. A set-based single update is the optimal way of doing things.
July 24, 2008 at 7:36 am
Correlated subqueries in the select clause (which you have lots and lots of) run multiple times depending on how many rows are in the outer query. You essentially have a...
July 24, 2008 at 6:35 am
Tejwant Kaur (7/23/2008)
then use a while loop (not a cursor) to do this.
Not much difference.
Tables are unordered sets. Without a column to define an order, there is no 'Top'...
July 24, 2008 at 5:21 am
It's a little hard to read formatted like that
Are all of the ISNULLs necessary? Without the table def I can't say for sure, but some of the columns wrapped in...
July 24, 2008 at 5:17 am
take the exec out, put the print back and see what the built up sql string looks like.
July 24, 2008 at 5:15 am
It does smell like a parameter sniffing problem. See the three articles on parameter sniffing linked from this page[/url].
Any chance of posting the proc so that we can take a...
July 24, 2008 at 3:48 am
Hari.Sharma (7/24/2008)
Freeing the procedure cache causes, for example, an ad hoc SQL statement to be recompiled instead of reused from the cache.
As well as every other procedure and query....
July 24, 2008 at 3:44 am
The safest fix is probably to completely drop the replication and recreate it.
July 24, 2008 at 3:31 am
faheemlatif (7/24/2008)
Hi all,is there any option or HINT for insert statament using that i can increse my insert statement speed.
SQL doesn't have a RUNFASTER hint, if that's what you're asking....
July 24, 2008 at 3:30 am
Not offhand. It could be a throttling within express. Lower avg CPU but the same overall CPU usage. Don't know for certain, just a guess.
If you want to test performance,...
July 24, 2008 at 2:24 am
If it's 64 bit, you should really set the max memory setting for SQL. I've seen too many cases of runaway memory allocation.
If you're using enterprise edition, make sure that...
July 24, 2008 at 1:33 am
Viewing 15 posts - 45,481 through 45,495 (of 49,571 total)