Viewing 15 posts - 5,731 through 5,745 (of 7,608 total)
The db must be SQL 2000, or in SQL 2000 compatibility mode (80).
Yikes and gadzooks! You need to move it forward to at least 2005 as fast you can,...
October 7, 2014 at 10:55 am
New Born DBA (10/7/2014)
ScottPletcher (10/6/2014)
The index I suggested was on Company and Form_Name.
Do you think I should test it out in Dev and QA first before I add a clustered...
October 7, 2014 at 10:37 am
New Born DBA (10/6/2014)
ScottPletcher (10/6/2014)
New Born DBA (10/6/2014)
ScottPletcher (10/6/2014)
Add a clustered index to the "COLUMN_NEXT_ID" table on "Company" and "Form_Name".And how creating an index will help?:-D
It will avoid a full...
October 6, 2014 at 4:29 pm
New Born DBA (10/6/2014)
ScottPletcher (10/6/2014)
Add a clustered index to the "COLUMN_NEXT_ID" table on "Company" and "Form_Name".And how creating an index will help?:-D
It will avoid a full table scan, locking as...
October 6, 2014 at 4:06 pm
Suggested query below. If you're willing to add a nonclustered index, you can try the affect of adding the index below before running the query. I can't tell...
October 6, 2014 at 4:02 pm
Add a clustered index to the "COLUMN_NEXT_ID" table on "Company" and "Form_Name".
October 6, 2014 at 3:17 pm
Code below appears to confirm that. Although I did notice that if you added "TOP (100)", it became a KEYSET cursor, even w/o you explicitly indicating that.
DECLARE csr1 CURSOR...
October 3, 2014 at 10:28 am
Yes, because the cursor is DYNAMIC, at least based on my reading of BOL:
"
DECLARE CURSOR
...
FORWARD_ONLY
...If FORWARD_ONLY is specified without the STATIC, KEYSET, or DYNAMIC keywords, the cursor operates as a...
October 3, 2014 at 10:05 am
Agreed. I think sys.dm_db_index_operational_stats would be more useful to capture overall I/O, although it still doesn't link it to a specific query, unless you can do that yourself just...
October 3, 2014 at 9:08 am
Did you try -1 as the length? Just a guess, but that's how SQL represents "MAX" internally in its system tables.
October 2, 2014 at 2:48 pm
SQL will have to pull back all rows, then apply the WHERE conditions.
You need to add the relevant WHERE conditions:
WHERE oq.calldate > getdate() -1
AND oq.duration > ''00:00:20'''
to the remote query...
October 2, 2014 at 2:34 pm
Oldest active transaction:
SPID (server process ID): 149
UID (user ID) : -1
Name : user_transaction
LSN : (3978:123016:460)
Start time : Sep 29 2014 11:37:23:380AM
To be sure of the...
October 2, 2014 at 2:31 pm
If it's varchar, best would be to test it as varchar, thus not converting the column ... but that is only safe if all values are consistently left-padded with zero(s).
Either...
October 2, 2014 at 1:37 pm
Format 'YYYYMMDD hh:mm' is always accurately translated in SQL Server.
Therefore, you need just two STUFFs:
SELECT
varchar_data AS original_string,
CAST(STUFF(STUFF(varchar_data, 9, 0, ' '),...
October 2, 2014 at 1:16 pm
True, if they actually are using SQL 2012. Sometimes you can't be sure :-D.
October 1, 2014 at 3:12 pm
Viewing 15 posts - 5,731 through 5,745 (of 7,608 total)