Viewing 15 posts - 1 through 15 (of 19 total)
Well using a NOLOCK might mean that the engine is not putting a SELECT lock on the table (which it releases as soon as it obtains it).
Other than...
@SQLvariant
November 18, 2009 at 12:42 pm
Itzik Ben-Gan has a post somewhere about the pitfalls of WITH (NO LOCK) and the inconsistent data results it can cause. With SQL 2005+ I just depend of Read...
@SQLvariant
November 18, 2009 at 12:23 pm
hydbadrose (10/21/2008)
@SQLvariant
October 21, 2008 at 12:08 pm
Vivien Xing (1/9/2008)
Full TEST indexes? Full TEXT indexes!
@SQLvariant
September 20, 2008 at 5:35 pm
By default only the first 256 characters are returned in Query Analyzer/ Management Studio. To do increase this, go to the 'Results to Text' tab under Tools > Options >...
@SQLvariant
May 13, 2008 at 10:27 am
GilaMonster (5/13/2008)
You can log the output of:
SELECT * from sys.dm_exec_requests where session_id < 50
Log it every few sec. You should see...
@SQLvariant
May 13, 2008 at 10:21 am
I assume that you mean that each are setup in a Dev db on the same server.
What's the row count difference between the two?
Have statistics been updated in each db...
@SQLvariant
May 13, 2008 at 10:18 am
They should show up when you run profiler against your db.
@SQLvariant
May 13, 2008 at 5:36 am
nKognito (5/13/2008)
I have a one table with huge data size (its about millions records and gigabytes in size) and without any foreign keys. My actions are...
@SQLvariant
May 13, 2008 at 4:07 am
Jamie,
So then fire up Profiler.
Get a Trace ready to go.
about 30 seconds before the query is supposed to run, start the trace.
Stop the trace as soon as the CPU goes...
@SQLvariant
May 12, 2008 at 4:13 pm
How many disks are in your array?
I have a similar situation and routinely replicate hundreds of thousands - millions of rows in just a few seconds?
I guess that a better...
@SQLvariant
May 12, 2008 at 10:47 am
No.
I'm a member of Baarf. 😀
I would never do such a thing.
@SQLvariant
May 12, 2008 at 9:14 am
In my experience with OLTP SQL Servers restarting is a bad thing from a performance standpoint. You loose you're query plans.
Back in the SQL 2000 days if we rebooted...
@SQLvariant
May 12, 2008 at 9:10 am
Where is your distribution db located?
Is it on fast disks just like your transactional db that you are trying to replicate? If so, is it on the same set...
@SQLvariant
May 12, 2008 at 9:04 am
I'll just say that my experience was pretty positive.
It didn't eat up much CPU or I/O for us and virtually completely cleaned up our blocking issues.
I hoped that helped a...
@SQLvariant
May 12, 2008 at 8:52 am
Viewing 15 posts - 1 through 15 (of 19 total)