Viewing 15 posts - 55,126 through 55,140 (of 59,098 total)
Yep... you've got it... just wanted to make sure ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
September 10, 2007 at 2:39 pm
And, selecting more columns than you need may also cause high speed INDEX SEEKs to change to mere INDEX SCANs, not to methion the additional network traffic that selecting more...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 10, 2007 at 2:30 pm
Too bad that SET XML_SHOWPLAN ON doesn't work in SQL Server 2000, eh?
--Jeff Moden
Change is inevitable... Change for the better is not.
September 10, 2007 at 2:26 pm
You really want to learn? The best way to learn is to get good enough to teach. The only way to do that is to practice. The best way to...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 10, 2007 at 12:05 am
First, thank you for the high compliment.
The thing that makes it "set based" is the fact that only the effect on a column was considered. Yes, it appears that a...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 9, 2007 at 11:57 pm
It's the many that don't understand that we've run into in many a thread. Between the two of us, it's almost like a standing joke... except it's not funny.
--Jeff Moden
Change is inevitable... Change for the better is not.
September 9, 2007 at 11:47 pm
You may have to limit the amount of memory each server uses because each is looking for 2 gig for a total of 4 gig... no room for the apps...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 9, 2007 at 10:32 am
Seems to me, based on the chart that Matt posted and the low volume of your anticipated connection/data plans, standard edition would do.
--Jeff Moden
Change is inevitable... Change for the better is not.
September 9, 2007 at 10:24 am
I sure do feel for folks that get stuck in that type of situation. Definitely not a pleasant position. Was going to suggest you find a new company but you've...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 9, 2007 at 9:27 am
Heh... maybe it figured out that you're breaking the license agreement and, therefore, the law by using the Developer Edition for production? ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
September 9, 2007 at 9:20 am
Heh... yeah... I did noticed that... easier for them to throw hardware at the problem even though that doesn't work. Still makes them feel like they did something.
--Jeff Moden
Change is inevitable... Change for the better is not.
September 9, 2007 at 9:18 am
Oh yeah... almost forgot this... and speaking of "Thinking in Sets", Joe, you might want to include this in your new book... just because something is sans-loop, doesn't mean it's...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 8, 2007 at 9:40 pm
Yeah... how 'bout that? I'm thinking that a couple of us on this forum should get together and write our own book... one that has some useful info ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
September 8, 2007 at 7:04 pm
As a bit of a sidebar... why is it necessary to create a table named after a month and year??? ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
September 8, 2007 at 7:02 pm
NULL concatenated with anything is still NULL if the default setting of "Concatenate Null Yields Null" was left on... so this simple ditty will do the job you asked...
IsNull(@RbrComm+CHAR(13)+CHAR(10),'')
--Jeff Moden
Change is inevitable... Change for the better is not.
September 8, 2007 at 6:58 pm
Viewing 15 posts - 55,126 through 55,140 (of 59,098 total)