Viewing 15 posts - 37,036 through 37,050 (of 59,072 total)
To anyone else reading this particular thread...
The method Wayne used is affectionately known as the "Quirky Update" or the "Running Total Solution". It has rules that you MUST follow...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 29, 2010 at 6:42 am
Wayne,
I was looking at your previous row calculation on the 3 part update thinking to myself "Cool... he even thought of the forced RN change when EMID changes just...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 29, 2010 at 6:34 am
Aye... that's the ticket, matey!
--Jeff Moden
Change is inevitable... Change for the better is not.
August 29, 2010 at 6:10 am
Funny that you mention The Flash, Wayne... I'm always hungry like he is after a good run... especially after I quit smoking (finally).
--Jeff Moden
Change is inevitable... Change for the better is not.
August 29, 2010 at 5:43 am
pietlinden (8/28/2010)
Say for the sake of argument...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 28, 2010 at 2:20 pm
Thanks for the feedback, Brian. And you and I have said virtually the same thing now on NVARCHAR(MAX)... 2GB max storage requirement (same as VARCHAR(MAX)), 1GB max displayable characters....
--Jeff Moden
Change is inevitable... Change for the better is not.
August 28, 2010 at 2:13 pm
Since you have no data that we can actually play with, all I can do is give you a suggestion... see the following article...
http://www.sqlservercentral.com/articles/Crosstab/65048/
--Jeff Moden
Change is inevitable... Change for the better is not.
August 28, 2010 at 2:09 pm
You'd figure that after 7 hears on this site, that I'd have run into this fun and informative article by now. As an update, the SQL Server documentation now...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 28, 2010 at 2:02 pm
It's always fun to look at that stuff at the byte level. Thanks for posting it, Brian. 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
August 28, 2010 at 1:55 pm
Heh... now you're on it. And folks don't even have to hold office to do such a wonderful thing. Just show up. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
August 28, 2010 at 1:30 pm
Alvin Ramard (8/27/2010)
How many times must I repeat this? We do not need a DBA!!!!http://www.sqlservercentral.com/Forums/Topic976708-266-1.aspx#bm976772
Looks like someone's about to have a great weekend.
Let's hum them a work tune to...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 28, 2010 at 1:23 pm
CirquedeSQLeil (8/28/2010)
I'll never think of "comma delimited" in the same way againForum Post title:
To split comma delimiterd string
Has somebody been leaving hamster poo in here?:hehe:
Heh... nope. Wrong kind of...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 28, 2010 at 1:08 pm
It's not a matter of formatting with them... it's a matter of not destroying formatting with them.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 28, 2010 at 1:01 pm
Ariadne (1/9/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
August 28, 2010 at 12:59 pm
Brian O'Leary (8/28/2010)
TryWHERE [Timestamp] >= '2010-08-28 00:00:00.000' and [Timestamp] <= '2010-08-28 23:59:59.999';
Hi Brian,
That's not the recommended way to do things because 1)... 23:59:59.999 rounds UP to the next day for...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 28, 2010 at 12:50 pm
Viewing 15 posts - 37,036 through 37,050 (of 59,072 total)