Viewing 15 posts - 50,626 through 50,640 (of 59,099 total)
I know it sounds strange, but the first thing I'd try is dropping and recreating the function.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 12, 2008 at 7:37 pm
Matt Miller (5/12/2008)
Jeff Moden (5/12/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 12, 2008 at 7:26 pm
RyanRandall (5/12/2008)
Jeff Moden (5/12/2008)
Heh... not my blog, Ryan. I think that's Jeff Smith's, but I'm not sure.
LOL - yes I know it's not your blog. I guess you missed...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 12, 2008 at 6:37 am
ahsansharjeel (5/12/2008)
SELECT * , ROW_NUMBER() OVER(ORDER BY ID) AS MY_ROW_NUM FROM
(
SELECT ID, FirstName, LastName, JoinDate FROM Table1
UNION
SELECT ID, FirstName,...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 12, 2008 at 6:34 am
Instead of bailing from the company, you have a huge opportunity... set up a multi-million row test and show them why it's a bad idea. Challenge those that support...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 12, 2008 at 6:26 am
RyanRandall (5/12/2008)
Jeff Moden (5/12/2008)
Isn't CROSS APPLY just another name for "correlated sub-query"?
😛
It sure is, but if it's the fastest method, who cares? 🙂
It's something else to try, anyway, and I'm...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 12, 2008 at 6:23 am
How did you intend to place the results in a file? Also, can you use xp_CmdShell or not?
--Jeff Moden
Change is inevitable... Change for the better is not.
May 12, 2008 at 6:16 am
AT&T used to have whacky date/time codes like this so they could fit date/time in 8.3 file names.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 12, 2008 at 5:38 am
Just a thought... If you're coming in as a replacement for these DBA's and the replacement is not voluntary, I wouldn't expect a whole lot of cooperation. In fact,...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 12, 2008 at 5:31 am
How many rows are being output by the query? Also, are you outputing the query to the screen? If so, why?
--Jeff Moden
Change is inevitable... Change for the better is not.
May 12, 2008 at 5:27 am
Isn't CROSS APPLY just another name for "correlated sub-query"?
--Jeff Moden
Change is inevitable... Change for the better is not.
May 12, 2008 at 5:16 am
If you must use Excel for reporting, why not write a couple of SQL Server views and use "Get External Data" in Excel to interogate the views and seemingly "import"...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 12, 2008 at 5:13 am
The Tally table cannot be used to solve ranking problems because of the inherent cross-join. You've limited the cross-join, but only with a triangular join... half as bad but...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 12, 2008 at 5:09 am
srienstr (4/1/2008)
Jeff Moden (3/31/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 12, 2008 at 4:49 am
Nicely done, Ryan.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 12, 2008 at 4:35 am
Viewing 15 posts - 50,626 through 50,640 (of 59,099 total)