Viewing 15 posts - 45,466 through 45,480 (of 49,552 total)
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.
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
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...
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
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'...
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
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...
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
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.
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
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...
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
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....
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
July 24, 2008 at 3:44 am
The safest fix is probably to completely drop the replication and recreate it.
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
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....
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
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,...
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
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...
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
July 24, 2008 at 1:33 am
TempDB shouldn't be on C. It should have a dedicated physical drive, due to high usage it tends to get. Raid 1 or 10 if possible.
SQL always hogs memory. That's...
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
July 24, 2008 at 1:19 am
Available memory's a bad measure. SQL will, by design, take memory if it is available and if the max memory has not been set.
Express is limited to 1 GB...
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
July 24, 2008 at 1:16 am
Anyone noticed that this thread is 3 years old?
Hans, can you start a new thread and explain your problem please?
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
July 24, 2008 at 1:12 am
CPU is time spent on the CPU in miliseconds
Reads and Writes are the number of pages (8k) read or written by the query
Duration is the total time taken for the...
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
July 24, 2008 at 12:58 am
Viewing 15 posts - 45,466 through 45,480 (of 49,552 total)