Viewing 15 posts - 43,951 through 43,965 (of 59,101 total)
Paul White (5/2/2009)
Jeff Moden (5/2/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 2, 2009 at 5:56 pm
Paul White (5/2/2009)
Well spotted! I must admit I looked at it and gave up after a few minutes...I guess replacing LEN with DATALENGTH might fix it up too?
Paul
Yes... but...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 2, 2009 at 5:36 pm
george sibbald (5/2/2009)
that would upset the heck out of most auditors unfortunately.
Why? I would think that the lack of security setup by the DBA that allowed it's misuse would...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 2, 2009 at 5:11 pm
Phil Factor (5/2/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 2, 2009 at 5:00 pm
For the most part, if you have defined a linked server, there is usually no need at all for OPENQUERY or anything like it. Just use a 4 part...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 2, 2009 at 1:27 pm
Heh... I'm definitely NOT an ANSI purest and I definitely DON'T believe in the myth of portable code especially when it comes to high performance batch code.
For all the advantage...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 2, 2009 at 1:03 pm
george sibbald (5/2/2009)
as part of the same job enable xp_cmdshell just before the bcp and disable it again immediately afterwards
That would certainly work... I guess my question would be...
If...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 2, 2009 at 12:43 pm
troy.hodge (5/1/2009)
I want to confirm that is infact correct and a good Idea. Are their short comings to this approach? Any reason we would not want to do this?
Some of...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 2, 2009 at 12:21 pm
Phil Factor (5/2/2009)
but I hit problems with the UPDATE ... FROM query, whist using variables. SQL Server Bugs, I'm afraid.
Which bugs?
--Jeff Moden
Change is inevitable... Change for the better is not.
May 2, 2009 at 11:15 am
m.berggren (5/2/2009)
Maybe there is something wrong when I create the table...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 2, 2009 at 10:59 am
john.arnott (5/2/2009)
Sorry for any confusion; I'm not the original poster. He posted in the SQL 2000 forum with just a snippet of code -- no table def's, nothing to...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 2, 2009 at 10:55 am
Any feedback on this, Jim?
--Jeff Moden
Change is inevitable... Change for the better is not.
May 1, 2009 at 9:32 pm
john.arnott (4/30/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 1, 2009 at 9:25 pm
m.berggren (4/30/2009)
Jeff:How does this so called "anchor" field works ?
Here are a helpful link about statements in SQL Anywhere Studio 9.0.2
http://www.ianywhere.com/developer/product_manuals/sqlanywhere/0902/en/html/index.html
Regards
Magnus
Matt Miller did some testing and claimed that without it,...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 1, 2009 at 9:20 pm
john.arnott (4/30/2009)
But this is SQL 2000.....
I thought you said you were using SyBase.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 1, 2009 at 9:17 pm
Viewing 15 posts - 43,951 through 43,965 (of 59,101 total)