Viewing 15 posts - 46 through 60 (of 309 total)
If it is blocking users until all inserts have finished you probably have a transaction running that spans all inserts. How is the script started?
October 15, 2010 at 4:58 am
To find the most expensive queries you could for example use code like this:
SELECT top 20
max_elapsed_time/1000000.0 as max_duration,
total_elapsed_time/1000000.0 as total_duration,
execution_count,
char(13)+char(10)+
(SELECT SUBSTRING(text,statement_start_offset/2,(CASE WHEN statement_end_offset = -1 then LEN(CONVERT(nvarchar(max), text)) *...
October 15, 2010 at 4:54 am
I find it unlikely that the cast to nvarchar is causing your performance problems. If you are updating a large number of rows, most of the time is probably spent...
October 15, 2010 at 4:32 am
hahnorlaska (10/12/2010)
The issue with the Except is that it only exists to handle the rare (relatively) occasion where something went wrong as the process is...
October 13, 2010 at 1:09 am
I have SQL2008 development edition SP1 CU6
select @@version
Microsoft SQL Server 2008 (SP1) - 10.0.2757.0 (X64) Jan 8 2010 19:55:08 Copyright (c) 1988-2008 Microsoft Corporation ...
October 12, 2010 at 11:58 am
hahnorlaska (10/12/2010)
October 12, 2010 at 11:09 am
It works for me with a test script.
You can see how the following works for you:
use tempdb
GO
CREATE TABLE [dbo].[geo1](
[id] [int] IDENTITY(1,1) NOT NULL,
[latlong] [geography] NULL,
CONSTRAINT [PK_geo1] PRIMARY KEY CLUSTERED...
October 12, 2010 at 9:05 am
Your problem is caused by how SQL server estimates the number of rows for a statement like
select ... from PART where PARTNAME LIKE @p
In the posted execution plan you...
October 12, 2010 at 8:04 am
I totally agree with bitbucket.
Please read the first link in his signature.
Your need to make your question much clearer.
At a minimum you need to post sample data in the form...
October 12, 2010 at 6:47 am
The fill factor only applies when an index is created or rebuilt.
SQL server does not try to maintain the fill factor when updating or inserting values.
Quote from BOL:
The fill factor...
October 12, 2010 at 6:24 am
I suggest you break up the query in two parts using a temporary table.
First select the duplicates into a temporary table.
Then insert all data not included in the duplicate table.
The...
October 12, 2010 at 5:55 am
160 is a non-breaking space.
You very often get such characters if you copy and paste text from the web.
August 25, 2010 at 9:19 am
YSLGuru (8/20/2010)
Well this test of creating a duplicate index by a differnet name has appeared to of worked. The purge tool ran to completion without errors and the Index...
August 20, 2010 at 3:52 pm
The main problem with INSERT INTO is that it creates a lot of log when inserting large amounts of data. SELECT INTO is minmally logged which means that it is...
August 20, 2010 at 3:24 pm
BULK INSERT is only used to insert data from a file into a table.
When copying data between two sql server tables you could either use SSIS or you could use...
August 20, 2010 at 1:02 pm
Viewing 15 posts - 46 through 60 (of 309 total)