Viewing 15 posts - 40,576 through 40,590 (of 59,098 total)
This is an "Ordinal Rank" problem. The following has your SQL Server 2000 answer along with a code example and all the things you must do to pull this...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 21, 2009 at 8:03 pm
homebrew01 (12/21/2009)
CirquedeSQLeil (12/21/2009)
Then a simple select * into tablebackup12212009 from table would suffice for the backup.
I seem to recall that you can get blocking when creating a table this way...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 21, 2009 at 7:41 pm
Heh... you have a triangular join, a while loop, and XML and still want to know why this is slow? 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
December 21, 2009 at 7:39 pm
Yes I could... but since this is likely an interview question or homework question and one of the skills a DBA must demonstrate is how to find out answers to...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 21, 2009 at 7:36 pm
BWAA-HAA!!! Frosty needs to get a set-based decoder ring! 😛
DECLARE @ToAllGoodPeople TABLE
(
RowNum INT,
...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 21, 2009 at 7:24 pm
In plain English, what is it that you're trying to do?
--Jeff Moden
Change is inevitable... Change for the better is not.
December 21, 2009 at 6:07 pm
Before you set autogrow to anything, you need to find out what is causing the autogrowth. Like you've said, you've probably patched beyond the point of the fault. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 21, 2009 at 6:02 pm
BCP won't hold a table open like that. Something else has a grip on the table.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 21, 2009 at 5:55 pm
Ok... so let's peel one potato at a time. My first question would be.... did you try just removing the "GO"'s?
--Jeff Moden
Change is inevitable... Change for the better is not.
December 21, 2009 at 5:50 pm
So, you're all set then?
--Jeff Moden
Change is inevitable... Change for the better is not.
December 21, 2009 at 5:48 pm
The problem isn't with how cursors work... the problem is with how databases work. For SELECT statements, the only way to guarantee an order of the result set is...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 21, 2009 at 8:46 am
calico-604598 (12/20/2009)
With SQL Server 2005 Expresse Edition CMDSHELL can be enable / disable with sp_configure or with surface area.
I ask this question because I dont want to manually enable...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 21, 2009 at 8:01 am
Thanks, Daipayan,
Just wanted to make sure you were covered on this. Lot's of folks simply do it wrong and they end up with a huge performance problem on their...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 21, 2009 at 7:58 am
SQL Server is running the CLR... SQL Server must be runing as a user that has the privs to "see" the UNC.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 21, 2009 at 7:55 am
Heh... got it and thanks for taking the time to explain.
Depending on how you're pushing that to Excel, it's likely that the trailing 0's just won't matter... Excel...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 21, 2009 at 7:53 am
Viewing 15 posts - 40,576 through 40,590 (of 59,098 total)