Viewing 15 posts - 57,796 through 57,810 (of 59,101 total)
Just a bit of clarification... I've not tested WHERE NOT IN vs OUTER WHERE NULL on sp4... I've seen several differences in execution plans between sp3a and sp4...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 3, 2006 at 9:41 pm
It would usually be someone who has a role of "Domain Admin" (I think that's what they call it but not sure... I'm not a network type of guy).
--Jeff Moden
Change is inevitable... Change for the better is not.
September 3, 2006 at 9:38 pm
WHERE IN is not normally an acceptable substitute for a good old fashioned inner join or equi join and tends to be a bit slower. WHERE NOT IN, however, has...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 3, 2006 at 9:36 pm
| While Steve's post may have been pushing the boundaries a little Jeff, I still appreciate his response. |
If you're...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 3, 2006 at 8:26 pm
Not sure how I'd pose the question in such a manner to see how many DBAs could get the answer right without using QA... any ideas?
--Jeff Moden
Change is inevitable... Change for the better is not.
September 3, 2006 at 6:31 pm
If you wish to delve into semantics, I suppose you are correct. Still, you didn't meet the spirit of the original posting nor have any of the 23 posts you've...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 3, 2006 at 2:14 pm
In order to use non-local UNC's, the server services must start with a windows login that has access to the UNC's desired. Our DBA's setup a special "SQLDBA" user (with...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 3, 2006 at 12:22 pm
Sreejith,
Good code but if you run it more than once, it inserts additional new "Expired" records for the same ticket(s) that already have "Expired" records... you forgot to check to...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 3, 2006 at 12:14 pm
An hour for 30k records? Obviously, that's not good... I'm thinking that the ORDER BY is what is really slowing things down but I could be wrong... the UNIQUE IGNORE DUPLICATE...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 3, 2006 at 11:44 am
That's one of the things I admire about you, Remi... absolute integrity and honesty...
Here's a couple of links I was involved with that explain it all...
http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=8&messageid=243646&p=2
http://www.planet-source-code.com/vb/scripts/ShowCode.asp?txtCodeId=1073&lngWId=5
--Jeff Moden
Change is inevitable... Change for the better is not.
September 3, 2006 at 11:37 am
Absolutely correct, Remi... you and I both know that "open text" columns that contain multiple pieces of data (city,state... full name, etc) are the absolute worst and will usually require...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 3, 2006 at 10:02 am
It means the deadlock occurred on an Index level rather than a table or a page...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 2, 2006 at 11:04 pm
You don't need dynamic SQL for this...
drop table #test
CREATE TABLE #Test( FieldOne varchar(10),
FieldTwo integer)
DECLARE @Parameter1 integer
SET @Parameter1 = 1
INSERT INTO #Test
SELECT 'Test...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 2, 2006 at 10:50 pm
There's several ways to do this... here's one if you have SA privs... there are other methods if this one doesn't suit ya... let us know...
DECLARE @Cmd VARCHAR(8000)
SET @Cmd =...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 2, 2006 at 10:40 pm
Are you talking about having SQL Server send email?
--Jeff Moden
Change is inevitable... Change for the better is not.
September 2, 2006 at 10:35 pm
Viewing 15 posts - 57,796 through 57,810 (of 59,101 total)