Viewing 15 posts - 42,316 through 42,330 (of 59,102 total)
Is the "wholerow" text stored as VARCHAR(8000) or VARCHAR(MAX)? If it's VARCHAR(MAX), does it need to be? Since VARCHAR(MAX) is inherently "out of row" (or whatever you want...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 14, 2009 at 2:28 pm
Bob's method eliminates the use of a cursor. If you need to "productionalize" something like that, we can do a little XML concatenation into a variable using his good...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 14, 2009 at 2:14 pm
gah (8/14/2009)
Plase excuse my ignorance, but how much is a "crore"?does one "crore" represent ten million (10,000,000) ?
gah
From WikiPedia.com...
A crore (Hindi: ?????) (often abbreviated cr) is a unit in...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 14, 2009 at 1:40 pm
For quick and dirty stuff like that, GOOGLE the undocumented sp_MSForEachDB extended stored procedure. It's got a nasty cursor in it but it is convenient for this type of...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 14, 2009 at 1:30 pm
Heh... yeah, I forgot about that. Add TOP 2000000000 to the SELECT in the CTE. Don't use TOP 100%... although I haven't had the time to verify it,...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 14, 2009 at 1:17 pm
GilaMonster (8/14/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
August 14, 2009 at 1:12 pm
RBarryYoung (8/14/2009)
Jeff Moden (8/14/2009)
RBarryYoung (8/11/2009)
WayneS (8/11/2009)
...BTW, I think Jeff calls it the "pseudo-cursor". Isn't it Phil that calls it the "quirky update"?
Nah, that's me. Jeff hates the term "pseudo-cursor"...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 14, 2009 at 11:07 am
RBarryYoung (8/14/2009)
Wayne: Any chance we could get some Create Table defs & sample data Inserts?
See Paul's post... it's the same stuff as before (I think).
--Jeff Moden
Change is inevitable... Change for the better is not.
August 14, 2009 at 11:05 am
RBarryYoung (8/11/2009)
WayneS (8/11/2009)
...BTW, I think Jeff calls it the "pseudo-cursor". Isn't it Phil that calls it the "quirky update"?
Nah, that's me. Jeff hates the term "pseudo-cursor" and much prefer's...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 14, 2009 at 10:41 am
Ah.... my bad, Nigel. More coffee please. :blush: I was thinking of the returns from some commands. Thank you for the catch.
Still, 8191 can be a...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 14, 2009 at 10:19 am
Command lines are limited by the system to only 255 characters and I don't know if they can actually be of the NVARCHAR data type (never tried it). Obviously, VARCHAR(MAX)...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 14, 2009 at 9:18 am
Lowell (8/14/2009)
you cannot reuse the numbers if there are gaps...at least not easily.
I'd like to add to that.... there is no reason to "fill in the gaps". If a...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 14, 2009 at 9:13 am
josh.d.kelly (8/13/2009)
I am a web developer trying to become a better database designer. I have been reading about keeping away from lookup tables.
Do you have a URL where you've been...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 14, 2009 at 12:44 am
Do what the comments in the following state and try it again. Let me know if it helped...
;WITH
cteSplit AS
(
SELECT s.RowNum,
Element = ROW_NUMBER() OVER (PARTITION BY...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 14, 2009 at 12:21 am
Heh... I had similar feelings about some of the posts. Some of it was so wrong I was moved to say "I'll also say that a lot of the...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 13, 2009 at 10:40 pm
Viewing 15 posts - 42,316 through 42,330 (of 59,102 total)