Viewing 15 posts - 47,971 through 47,985 (of 59,102 total)
Actually, there is a direct replacement for RowNum=1 in SQL Server... it's called TOP 1. 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
October 3, 2008 at 8:25 pm
Cross post... please don't answer on this thread... go to the following instead...
http://www.sqlservercentral.com/Forums/Topic580370-1291-1.aspx
--Jeff Moden
Change is inevitable... Change for the better is not.
October 3, 2008 at 8:22 pm
Still, the deed is done and the OP is gonna whack the internal documentation in someone's DB. Questions like this should simply go unanswered. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
October 3, 2008 at 8:14 pm
Franco_1 (10/3/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 3, 2008 at 8:05 pm
And, yet, we so no testing nor references to Microsoft articles on the subject... does anyone have proof one way or the other? 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
October 3, 2008 at 8:01 pm
jlp3630 (10/3/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 3, 2008 at 7:51 pm
jeremiah.peschka (10/3/2008)
Likewise, CLR functions have an even larger performance advantage over T-SQL functions for complex computation, string manipulation, and business logic.
With the exception of RegExReplace, many of us have been...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 3, 2008 at 7:48 pm
lcjohnson (10/3/2008)
I found the script to kill the users. Thanks.
Use with great caution! If you hit the wrong SPID, you can tank the server or some critical poorly written...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 3, 2008 at 7:45 pm
Heh... You're all destroying the ability to produce an automated data dictionary for a database and none of you even bat an eyelash at that. :blink: Sure, sure......
--Jeff Moden
Change is inevitable... Change for the better is not.
October 3, 2008 at 7:27 pm
Okidoki... first off, since you didn't provide any table creation scripts nor data population scripts, you have to understand that I've not tested this code. Please see the link...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 3, 2008 at 7:05 pm
vidhyasudha (10/3/2008)
Sorry for all the inconvenience caused.
Tab1 structure
Create Table Tab1
(
name varchar(25),
description varchar(25),
Category varchar(25)
)
Sample data for Tab1
insert into tab1 (name,description,category) values ( 'caneditacc','editing','Acc')
insert into tab1 (name,description,category) values ('candeleteacc','deleting','Acc')
insert...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 3, 2008 at 6:28 pm
There are a lot of things that will qualify as a date that will fail the conversion using date format 103. For example, 0 is a valid date. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 3, 2008 at 6:19 pm
I don't personnally know how to do it, but the folks at my old shop did it quite easily. Apparently, certain SANs come with the ability to make snapshot...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 3, 2008 at 6:06 pm
Yep... I absolutely agree with Richard that batch size is important... trying to import 20 million rows will drive the log file absolutely nuts if you don't do the Bulk...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 3, 2008 at 5:59 pm
It doesn't need to be that complicated if you understand that NULL is NOT nothing and cannot be compared to using relational operators...
IF (SELECT somecolumn FROM sometable) > ' '
PRINT...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 3, 2008 at 5:52 pm
Viewing 15 posts - 47,971 through 47,985 (of 59,102 total)