Viewing 15 posts - 23,221 through 23,235 (of 59,102 total)
Heh... you're not alone... lack of coffee has caused more than one mistake on my part. That's why I have to keep it simple... "so I doan gotta think...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 14, 2014 at 6:41 am
Using the KISS method, this should work ok in SQL Server 2000. Details are in the comments,
--===== Build a test table.
-- This is not...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 13, 2014 at 11:33 pm
Evil Kraig F (7/10/2014)
ChrisM@Work (7/10/2014)
Koen Verbeeck (7/10/2014)
Jack Corbett (7/10/2014)
Koen Verbeeck (7/10/2014)
I saw Jeff was...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 13, 2014 at 8:12 pm
KoldCoffee (7/12/2014)
because I explained to you at least a couple of times, I can't use the ssis package because it is a slow solution. Therefore I'm not using SSIS.
Heh... OK....
--Jeff Moden
Change is inevitable... Change for the better is not.
July 13, 2014 at 5:00 pm
autoexcrement (7/10/2014)
I thought that went without saying, but yes I should have specified! 🙂 Table-Valued Functions will be many times faster than Scalar Functions!
Apologies. I used an abbreviation that...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 11, 2014 at 8:54 am
autoexcrement (7/10/2014)
It may also be possible to re-write your SP as a Function and use CROSS APPLY. Just thinking out loud.
That's actually a good idea if it can be written...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 10, 2014 at 9:36 pm
Robert Davis (5/24/2006)
Try adding a USE statement to the dynamic SQL.<DT><FONT color=#1111ff>set</FONT><FONT size=2><FONT color=#1111ff> @sql</FONT> </FONT><FONT color=#808080 size=2>=</FONT><FONT size=2> N</FONT><FONT color=#ff0000 size=2>' USE [OtherDatabase] <DT>create function dbo.fn_tot_alldbs(@yourparameter int) <DT>returns int...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 10, 2014 at 9:31 pm
aochss (7/10/2014)
Msg 8152, Level 16, State 14, Line 1
String or binary data would be truncated.
The statement...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 10, 2014 at 9:23 pm
jgoodwin 14842 (7/10/2014)
--Jeff Moden
Change is inevitable... Change for the better is not.
July 10, 2014 at 12:04 pm
sgmunson (7/10/2014)
--Jeff Moden
Change is inevitable... Change for the better is not.
July 10, 2014 at 12:01 pm
There's no need to avoid cursors for such a thing. They're not the issue in such instances. The issue would be, what does the stored procedure do and...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 10, 2014 at 11:58 am
Alan.B (7/10/2014)
Phil, you can make this more than twice as fast by turning it into an inline table value function like this:
To that, I say... are you sure? Please...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 10, 2014 at 11:23 am
Welsh Corgi (7/10/2014)
For example
ANDPromo.[Group] IN (''FL_Small'',''FL_Large'')
Also it generates this code that I do...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 10, 2014 at 11:19 am
sgmunson (7/10/2014)
DECLARE @DATE AS datetime = '07/10/2014';
DECLARE @TIME_START_INT AS int = 820;
DECLARE @TSV AS varchar(4) = RIGHT('00' + CAST(@TIME_START_INT AS varchar(4)), 4);
DECLARE @TIME_END_INT AS int =...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 10, 2014 at 10:37 am
To be honest, MS spends a shedload of time deprecating and removing things, some of which are incredibly useful. For example, just because many folks don't understand what ISNUMERIC...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 10, 2014 at 10:33 am
Viewing 15 posts - 23,221 through 23,235 (of 59,102 total)