December 9, 2009 at 6:02 pm
After seeing that code, my immediate recommendtion would be to lookup INSERT/SELECT in Books Online (instead of INSERT/VALUES) so that when someone explains how to fix this, you'll actually understand. And no... I'm not being a smarty pants about this... I'm dead serious.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 10, 2009 at 6:58 am
So, would this be a good example?
http://technet.microsoft.com/en-us/library/ms189872.aspx
And how is it related to my post? Little Lost here..
December 10, 2009 at 7:28 pm
doran_doran (12/10/2009)
Little Lost here..
BWAA-HAAA!!! Apparently, so I am! :blush: My response was supposed to go on another post that I was looking at at almost the same time.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 11, 2009 at 6:35 am
Wow - click on the error and it takes you there - FAB!
We need a 'handy tip of the day'!
This would have saved me hours by now.
I guess the trouble is that if you just pick up SQL Server after using other DBs (or much earlier versions etc) and don't go on training courses or have more knowledgeable peers then you just don't get to know these handy hints.
Mike Tanner
December 11, 2009 at 7:23 am
SQL-939141 (12/11/2009)
Wow - click on the error and it takes you there - FAB!We need a 'handy tip of the day'!
This would have saved me hours by now.
I guess the trouble is that if you just pick up SQL Server after using other DBs (or much earlier versions etc) and don't go on training courses or have more knowledgeable peers then you just don't get to know these handy hints.
Mike Tanner
It took me years to realize that, and I started on SQL Server. I don't even remember how I finally figured it out.
Viewing 5 posts - 31 through 34 (of 34 total)
You must be logged in to reply to this topic. Login to reply