Viewing 15 posts - 35,416 through 35,430 (of 59,099 total)
Double post. No posts here, please. Please refer to the other post at the following URL:
http://www.sqlservercentral.com/Forums/Topic1045849-391-1.aspx
--Jeff Moden
Change is inevitable... Change for the better is not.
January 11, 2011 at 7:36 am
Agreed... either one would do a nice job on such an article.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 11, 2011 at 7:13 am
durai nagarajan (1/11/2011)
Hi,the data you are pulling from sql server should have month as a field.
then populate the month in matrix header side and the data as desired.
hope this helps.
Do...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 11, 2011 at 7:11 am
bicky1980 (1/10/2011)
Jason Norsworthy (12/19/2010)
select * from
(
select *,
row_number() over(partition by...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 10, 2011 at 7:42 pm
mazzz (1/10/2011)
Frances L (1/10/2011)
well , I think if there 100%. then it will different. Thx.True. Trust me to worry about decimals and miss the obvious 🙂
Did you also check it...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 10, 2011 at 7:34 pm
sqldoubt (1/10/2011)
... and get output as an comma separated list and insert the output values to a table.
I have to tell you that's a very bad thing to do...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 10, 2011 at 7:27 pm
Steve Jones - SSC Editor (1/10/2011)
This might help: http://www.sqlservercentral.com/articles/Array/70702/Depending on how you structure things, you need to parse your procedure.
Heh... No! 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
January 10, 2011 at 7:22 pm
Craig Farrell (1/10/2011)
mister.magoo (1/10/2011)
mounish (1/10/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
January 10, 2011 at 7:07 pm
WayneS (1/10/2011)
Craig Farrell (1/10/2011)
GSquared (1/10/2011)
Since you're using SQL 2008, can you switch from delimited lists of parameter values to a table variable parameter? Those are more efficient.
I haven't had...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 10, 2011 at 7:03 pm
MonsterRocks (1/9/2011)
CREATE TABLE #TAB2 (SNO INT, UNQ_ID BIGINT)INSERT INTO #TAB2 VALUES(1,10)
i have to increament the value of UNQ_ID by 1 and assign it in one variable....
how it...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 10, 2011 at 7:00 pm
I guess I'd like to know why this has to be in dynamic SQL to begin with.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 10, 2011 at 6:47 pm
Now, THAT'S a Table Spool. Just the estimate, I know, but a 101million row spool? No wonder those distincts are crying.
That's your basic accidental cross join usually caused by a...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 10, 2011 at 6:45 pm
BaldingLoopMan (1/10/2011)
also it is bad proctice to default ur input params to null. If its a varchar it's not so bad however dates. Not so good.
I have to ask... why?...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 10, 2011 at 6:34 pm
Gabe,
I agree with Craig... which tag keys do you want to use up first? Also, what do you want to do if you don't have an exact match for...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 10, 2011 at 6:18 pm
BaldingLoopMan (1/10/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
January 10, 2011 at 6:12 pm
Viewing 15 posts - 35,416 through 35,430 (of 59,099 total)