Viewing 15 posts - 1,576 through 1,590 (of 2,043 total)
That is a huge difference. Could it be the amount of data returned?
Query analyzer displays the results faster in grid than in text mode.
What is the connection technology to sql server...
February 21, 2006 at 11:03 am
assuming listingid is the primary key
Step 1:
Create a temporary table with an idenity field (listingid, autoid)
INSERT into mytemptable
SELECT ListingID
from (SELECT ListingID from mytable order by newid)
Step 2:
update mytable
set displayorder=autoid
from mytable...
February 21, 2006 at 10:51 am
I wasn't aware of that one.
Good you've found it.
February 19, 2006 at 6:32 am
*Is it possible that a bad query to cause this behaviour
I can't say for sure. There is an issue with superfast I/O where a query can monopolize I/O access...
February 18, 2006 at 6:41 am
Got puzzled again.
Do you wish to capture 1/0 (the exit code)
or the number of failed attempts?
February 17, 2006 at 12:38 pm
Instead of reading a file byte per byte (1 I/O per byte) , a program can read them in chunks of y bytes (1 I/O command for y bytes in total)
The same...
February 17, 2006 at 12:35 pm
Simply because there is no recordset in sp_IsValidLogon, just a return code.
You want to capture the exit code?
February 17, 2006 at 10:55 am
You're welcome 🙂
Keep in mind that set-based solutions are likely faster than record by record based solutions in sql
February 17, 2006 at 2:17 am
not sure if this works
select proj_name as [project name], proj_nbr as [project number] from proj
February 16, 2006 at 2:33 pm
Sergiy query looks more plausible.
*edit just a test-query
This code should be tested first
DECLARE @begin datetime
DECLARE @end datetime
select ALLSWEEPS.barcode,ALLSWEEPS.ALL_COUNTS-ISNULL(SWEEPDOUBLES.DOUBLES,0)
FROM
(
select barcode,count_BIG(*) AS ALL_COUNTS all /*all...
February 16, 2006 at 2:26 pm
Please feed us some more information.
1) What is the current patch level of sql server and the os it runs on?
2) Did anything change just before the slowdown cropped up...
February 16, 2006 at 1:44 pm
can you remove the line
Set rstStoredProc = adocmd.Execute
February 16, 2006 at 11:47 am
*Declared: do you have a line
Set rstStoredProc= Server.CreateObject("ADODB.Recordset")
*Is your connection string correct? (see error object not open)
From http://www.connectionstrings.com/
Trusted_Connection=yes is for ODBC whilst you are using OLEDB
*oledb
"Provider=sqloledb;Data Source=REMITCOCLTVOL;Initial Catalog=REMITCOSQLServer;Integrated Security=SSPI;"
February 16, 2006 at 10:22 am
Something like this?
SELECT Table1ID1.targetInformation AS target1,Table1ID2.targetInformation AS target2
FROM Table2 LEFT JOIN Table1 Table1ID1 ON table2.ID1=Table1ID1.ID /*fill with NULL if not present in table1*/
LEFT JOIN Table1 Table1ID2 ON table2.ID2=Table1ID2.ID
ORDER BY Table2.ID
February 16, 2006 at 5:05 am
At the linked server properties
you can set how your account will be "transferred" across the network to the linked server.
Perhaps you can try with using the current login security context...
February 16, 2006 at 4:52 am
Viewing 15 posts - 1,576 through 1,590 (of 2,043 total)