Viewing 15 posts - 54,736 through 54,750 (of 59,072 total)
noeld (10/3/2007)
We know that, so far, we have been able to force...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 3, 2007 at 11:23 pm
Nothing undocumented... you need to look in BOL for the UPDATE... I've bolded the part of the update I used....
UPDATE
{
...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 3, 2007 at 11:10 pm
Tomm Carr (10/3/2007)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 3, 2007 at 11:06 pm
Peter,
Although the double correlated subquery will work, I'm also pretty sure it will kill batch performance because of the triangular join in it...
http://www.sqlservercentral.com/Forums/Topic359124-338-1.aspx#bm360151
--Jeff Moden
Change is inevitable... Change for the better is not.
October 3, 2007 at 7:31 am
Vishal,
Just a thought... Is this a permanent nonreporting you're modifiying? The reason I ask is if you're actually doing this to some "real" data (other than a reporting table),...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 3, 2007 at 7:22 am
I still don't know what "undocumented behaviour" Noel is talking about...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 3, 2007 at 7:11 am
Mahesh Gupta (10/2/2007)
What exactly do you mean by Max Length of the row ?
The maximum length of a row can be 8060 bytes. In this case, some of the...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 3, 2007 at 6:58 am
Ninja's_RGR'us (10/2/2007)
When was that?? I never saw it work like I want it to ;)... like the old one.
Actually, all that stuff worked... for about the first two days...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 3, 2007 at 6:56 am
Heh... already are... hardcore DBA just wouldn't allow this.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 3, 2007 at 6:50 am
Lowell (10/2/2007)
the thing about color is that you MUST enter the double quotes to get it to work.input = #0000FF is BAD
input = "#0000FF" is GOOD
Heh... thanks Lowell... but I...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 2, 2007 at 10:48 pm
Yeah, huh? Using loops comes highly unnatural to me. 😀 Goes against my data-troll grain.
The other place I saw it was with a splitter function that used a...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 2, 2007 at 10:44 pm
Bill,
I guess I don't understand why you are calling these procs as passthrough queries from Access... can't you schedule this as a job or run it through OSQL? That...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 2, 2007 at 10:35 pm
You can touch it. It won't hurt you.
Heh... and folks think Serqiy is a smartass??? :laugh:
Anyway, point well taken and I guess I have to eat a little crow on...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 2, 2007 at 10:27 pm
No... not true...
1. Editing a post still triple spaces the entire post.
2. Trying to post with [Code] still results in a triple spaced mess that doesn't obey leading...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 2, 2007 at 6:25 pm
Perfect... Nice "kick in" Peter... I'm gonna go back to sucking my thumb now... 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
October 2, 2007 at 6:15 pm
Viewing 15 posts - 54,736 through 54,750 (of 59,072 total)