Viewing 15 posts - 34,186 through 34,200 (of 59,099 total)
Welsh Corgi (4/23/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
April 23, 2011 at 3:46 pm
Jack Corbett (4/23/2011)
...you should not make blanket statements...
Heh... I've got a blanket statement... as always, "It Depends". 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
April 23, 2011 at 3:13 pm
Steve Jones - SSC Editor (4/23/2011)
As a general rule, I don't allow it, especially for non-sysadmins.
As a general rule, I agree and I don't normally allow humans , regardless or...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 23, 2011 at 2:51 pm
Edit: I should add, Jeff, I'm trying to prompt you into teacher mode a little on this. I'm not going to claim expertise on any of the older tools.. heck,...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 23, 2011 at 2:36 pm
Craig Farrell (4/23/2011)
I was thinking more along the lines of fixed width files for the format files then column skips.
Files with fixed width fields are no more difficult with BCP/BULK...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 23, 2011 at 2:14 pm
For more of a visual impact....
--===== Conditionally drop the test table to make reruns in SSMS easier.
-- (Note that this is NOT a part of...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 23, 2011 at 1:10 pm
Greg Snidow (4/22/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
April 23, 2011 at 1:04 pm
Understood. But the "old school" ways do work quite nicely including such things as you mention like incrementing file names, etc, etc. And, there's usually no need for...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 23, 2011 at 11:55 am
Heh... Yep. In fact, that's such a common request that I wrote an "SQL Spackle" article on the subject. Please see the following link...
http://www.sqlservercentral.com/articles/T-SQL/72503/
--Jeff Moden
Change is inevitable... Change for the better is not.
April 23, 2011 at 11:20 am
Fraggle-805517 (4/22/2011)
Jeff Moden (4/22/2011)
Shifting gears, if you still need help with this, let me know and I'll see what I can do over the weekend.
Below is what I ended up...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 23, 2011 at 12:20 am
r.vanlaake-1086273 (4/22/2011)
Not yet. I hoping to do some experiments with 64 bit ACE over this upcoming weekend. Thanks for the feedback on the 32 bit stuff. I'm glad they didn't...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 22, 2011 at 6:35 pm
getalok_akg (4/22/2011)
We have requirement to calculate the last data of the corresponding week .
Let me explain you the scenario , we are having time table that update on daily...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 22, 2011 at 6:10 pm
I guess I'll have to flip them back, then. I use BCP, SQLCmd, T-SQL and my old and dearly beloved ETL friend, xp_CmdShell especially when flat files for import...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 22, 2011 at 5:14 pm
AlexSQLForums (4/22/2011)
Jeff Moden (4/22/2011)
Thanks for the response, Alex, but won't that simply disable the ability of the proxy to use xp_CmdShell at all levels?
So is this proxy user also a...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 22, 2011 at 4:53 pm
It sounds like an interview or homework question but I'll cough up what I believe are the most important...
A Table Valued Function can be used in the FROM of a...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 22, 2011 at 10:51 am
Viewing 15 posts - 34,186 through 34,200 (of 59,099 total)