Viewing 15 posts - 48,196 through 48,210 (of 59,099 total)
I value F2F communications for many reasons... EMail, despite the presence of those bloody emoticons, don't tell you the emotion of the person... can't really tell if their mad, upset,...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 20, 2008 at 7:50 pm
Heh... Dude! I thought you said your buddy had it whipped.... 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
September 20, 2008 at 7:38 pm
I could be wrong, but I'm pretty sure there's no way to do it via T-SQL.
--Jeff Moden
Change is inevitable... Change for the better is not.
September 20, 2008 at 7:34 pm
Gotcha... good idea! Me... I use cocktail napkins. 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
September 20, 2008 at 7:25 pm
At least tell your buddy that there's errors in the data that he might not be aware of... dude... 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
September 20, 2008 at 7:23 pm
By the way... if you believe in paper instead of code, please read the Microsoft article at the following link...
http://support.microsoft.com/kb/153441/EN-US/
See where it says "NOTE: This problem does not apply to...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 20, 2008 at 7:07 pm
Man, I really appreciate you watching out for me, Sergiy. I've learned a lot from you. Thanks...
Ok... like I've done before when this controversy of Select/Into has come...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 20, 2008 at 6:50 pm
Exact same principles apply... but, now the requirements sound like homework. Recommend you take a look at Books Online and do your own homework... 😉
Good luck.
--Jeff Moden
Change is inevitable... Change for the better is not.
September 20, 2008 at 3:42 pm
Barry... nice blog! But why don't you write that stuff as articles on SSC? 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
September 20, 2008 at 3:37 pm
Ok... no error checking except for total number of rows. That also means, no primary key in this instance. You have to remove the primary key from the...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 20, 2008 at 11:59 am
Heh... Barry's post wasn't there when I started typing my response.
I agree, Barry... I used to call variables such as these "accumulators" which is also probably more appropriate.
"Pseudo Cursors"? ...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 20, 2008 at 9:41 am
bkDBA (9/19/2008)
Thanks. Good info. Have you actually tried it? Not trying to be a smart guy about this... I've heard that the auditing features of 2k8 are...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 20, 2008 at 9:27 am
Ninja's_RGR'us (9/19/2008)
Jeff Moden (9/18/2008)
Ninja's_RGR'us (9/18/2008)
Yes you need to create it first, including column definitions.
Heh... not exactly true...
SELECT *
INTO #MyHead
FROM OPENROWSET('SQLOLEDB','Server=(local);Trusted_Connection=Yes;Database=Master',
...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 20, 2008 at 9:23 am
Madhivanan (9/19/2008)
Jeff Moden (9/18/2008)
Ninja's_RGR'us (9/18/2008)
Yes you need to create it first, including column definitions.
Heh... not exactly true...
SELECT *
INTO #MyHead
FROM OPENROWSET('SQLOLEDB','Server=(local);Trusted_Connection=Yes;Database=Master',
...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 20, 2008 at 9:18 am
With error checking... broad subject... lemme start by asking what you want to do with the duplicate primay keys included in your sample file?
--Jeff Moden
Change is inevitable... Change for the better is not.
September 20, 2008 at 9:07 am
Viewing 15 posts - 48,196 through 48,210 (of 59,099 total)