Viewing 15 posts - 31,036 through 31,050 (of 59,101 total)
shah.simmy (2/20/2012)
hiplease help me with the solution for the following question:
These sound like "interview" questions and I don't normally answer such things. However, my answers for these types of...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 20, 2012 at 11:59 am
RobertYoung (2/19/2012)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 20, 2012 at 6:20 am
ThomasGr (2/20/2012)
with t as (select 1 x
union all
...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 20, 2012 at 6:12 am
Grant Fritchey (2/20/2012)
By the way, as far as posting goes, I didn't set...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 20, 2012 at 6:07 am
Cadavre (2/20/2012)
I'm surprised by the lack of responses, amongst those I socialise with away from work it has been a fairly major talking point.
Same here. Maybe folks on SSC...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 20, 2012 at 5:58 am
GPO (2/20/2012)
Who was the first person to come up with this (Jeff's) idea in the context of SQL Server? Was it Itzik Ben-Gan?
Yes, it was Ben-Gan. He used a...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 20, 2012 at 5:55 am
Thanks for the feeback and the participation, Tom. I've got a feeling that a whole lot of people just aren't interested.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 19, 2012 at 11:19 pm
Gosh... I know it's Sunday (well, early Monday now by my watch) but with more than 24 views, I hope more than 4 people take the poll.
Thanks, folks.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 19, 2012 at 10:31 pm
rajeev_vandakar-782919 (2/18/2012)
There is a table with 30 to 40 columns and hardly few columns may get updated by the user. We can't say which column(s) may...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 19, 2012 at 10:27 pm
Eugene Elutin (2/19/2012)
rajeev_vandakar-782919 (2/18/2012)
It's not totally possible, and anyway you would still better to write normal sql and update all 30-40 columns.
Not if you have triggers based on some of...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 19, 2012 at 10:16 pm
Charmer (1/24/2012)
herladygeekedness (1/24/2012)
In my opinion, if there is no column in which to check the criteria, you cannot use that criteria.
That said, not knowing...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 19, 2012 at 10:10 pm
e90fleet (2/19/2012)
300,000 rows returned to clog the proverbial...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 19, 2012 at 10:05 pm
dwain.c (2/19/2012)
I believe this solution will also work
Unfortunately, it doesn't. (See the results below). That's why I always ask for test data which the OP very nicely provided...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 19, 2012 at 9:47 pm
My recommendation would be to provide some test data for folks to work on so they might be better able to provide you with a coded answer. Please see...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 19, 2012 at 12:13 pm
bitbucket-25253 (2/18/2012)
http://www.sqlservercentral.com/scripts/CROSS+JOIN/87362/
Note that it is a SCRIPT so why oh why is it appearing in "Recent Posts" - another foul up something like...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 19, 2012 at 12:07 pm
Viewing 15 posts - 31,036 through 31,050 (of 59,101 total)