Viewing 15 posts - 42,916 through 42,930 (of 59,098 total)
Edward (7/14/2009)
Yep we are filling the gaps as we are reaching the min/max integer barriers.
Save yourself and others the pain... simply switch the column datatype to BIGINT. You will...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 19, 2009 at 11:09 pm
It's simple but no one ever answers my questions once I give an answer. With that in mind, please explain the business reason for wanting to do this. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 19, 2009 at 11:01 pm
WayneS (7/8/2009)[hrSo, just to make sure I have it correct, I should have used
from #tblTest with (TABLOCKX) OPTION (MAXDOP 1)Correct?
Correct. Man... sorry... I got way behind...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 19, 2009 at 10:58 pm
karthikeyan (7/9/2009)
Greg,They will pass it as STRING.
Why i need like this?
I have a table called country_exposure
create table country_exposure
(
Fund_Id int,
Malaysia decimal(16,8),
Philippines decimal(16,8),
Taiwan decimal(16,8),
Thailand decimal(16,8),
India decimal(16,8),
Austria decimal(16,8),
Belgium decimal(16,8),
Denmark decimal(16,8),
Finland decimal(16,8)
)
Really, really bad...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 19, 2009 at 10:54 pm
See the following for an answer...
http://www.sqlservercentral.com/articles/Test+Data/61572/
And please stop double and triple posting.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 19, 2009 at 10:50 pm
Jonathan Melo (7/9/2009)
Hi,Here's a way I developed to create dynamic SQL while maintaining some level of readability in the code.
Looks real familiar... especially the part about dynamic and static sections...
http://www.sqlservercentral.com/articles/cross+tab/65048/
--Jeff Moden
Change is inevitable... Change for the better is not.
July 19, 2009 at 10:45 pm
Using the test data provided, the following does the trick on the split and the answer number. You can take it from there...
--===== Declare a variable to hold the...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 19, 2009 at 10:33 pm
Greg Snidow (2/12/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
July 19, 2009 at 10:23 pm
vmon (7/8/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
July 19, 2009 at 10:16 pm
That's cool... so, are you suggesting a method sort IP addresses that aren't necessarily in the 3 digit byte format?
--Jeff Moden
Change is inevitable... Change for the better is not.
July 19, 2009 at 10:07 pm
http://www.sqlservercentral.com/articles/cross+tab/65048/
--Jeff Moden
Change is inevitable... Change for the better is not.
July 19, 2009 at 9:57 pm
Read this to solve the problem of an unknown number of columns.
http://www.sqlservercentral.com/articles/cross+tab/65048/
What I'd like to know is why do you need to denormalize data in such a fashion? Spreadsheet?
--Jeff Moden
Change is inevitable... Change for the better is not.
July 19, 2009 at 9:54 pm
kramaswamy (7/10/2009)
If that's the case, then the approach of updating one record at a time is probably the better one, despite looking ugly.
Ummm... no... not if it's done correctly. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 19, 2009 at 9:50 pm
Uh huh... the real question would be, "Why does this type of denormalization need to be done?" 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
July 19, 2009 at 9:39 pm
Heh... seriously...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 19, 2009 at 9:36 pm
Viewing 15 posts - 42,916 through 42,930 (of 59,098 total)