Viewing 15 posts - 54,046 through 54,060 (of 59,098 total)
Heh... personally, I'm glad banks are over-cautious with changes to software.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 21, 2007 at 8:04 pm
select EMPLNO,[Full Name],[CCNAME],[CC] from HREMP where [Full Name] like '%" & REPLACE(strS,'''','''''') & "%' and [CC] like '01032%' and (EMPSTATUS <> 90 or EMPSTATUS is null) order by [Full NAME];"
--Jeff Moden
Change is inevitable... Change for the better is not.
November 21, 2007 at 5:04 pm
Depends on what the maintenance plan is doing... DBCC REINDEX, can crush performance on very large tables that have large indexes or a CLUSTERED index that doesn't follow a chronilogical...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 21, 2007 at 4:59 pm
Vivien Xing (11/21/2007)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 21, 2007 at 4:52 pm
How about ...
Perfect...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 21, 2007 at 4:50 pm
EDIT: Actually, create a database on the new server with the same name as the database you're linking to on the old server. Create views which have the same name...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 21, 2007 at 4:21 pm
Why not just a Tally table driven split function, then?
--Jeff Moden
Change is inevitable... Change for the better is not.
November 21, 2007 at 4:15 pm
Matt Miller (11/19/2007)
Hey - if you're going to give me a new stapler, expect to find some things stapled.....:D
Heh! If that's true, guess I need to give you a lawnmower...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 21, 2007 at 4:10 pm
Joe Contreras (11/20/2007)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 21, 2007 at 4:01 pm
Heh... well said Robert and ALI...
Yeup... that's kinda the way I figure it but we're only guessing...
The bad part here is a huge opportunity was missed to help the users...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 21, 2007 at 3:43 pm
Jeff,
My apologies to you for incorrect comments. Anyhow, im still curious to see your version of it.
No, no... not a problem, Ramesh. And, the RowNumber Over Partition to...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 21, 2007 at 3:38 pm
Allen,
I'm not 100% sure because I don't have 2k5, but I don't believe that Ramesh's wonderfully easy to read code is going to do the trick for you because it...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 21, 2007 at 6:00 am
Jim,
Is this in reference to the table variable function you created that calls itself?
--Jeff Moden
Change is inevitable... Change for the better is not.
November 20, 2007 at 10:06 pm
I don't know what Celko's "Packing Join" is, but I think you're gonna need another column like a date/time or and IDENTITY column even if you were to use a...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 20, 2007 at 9:35 pm
"REVERSE" is pretty expensive performance-wise... PARSENAME still does the trick even with the modified list...
CREATE TABLE dbo.Hits (RowNum INT IDENTITY(1,1) PRIMARY KEY, Site VARCHAR(100))
INSERT INTO dbo.Hits (Site)
SELECT 'abc.support.microsoft.com' UNION ALL
SELECT...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 20, 2007 at 9:27 pm
Viewing 15 posts - 54,046 through 54,060 (of 59,098 total)