Viewing 15 posts - 44,731 through 44,745 (of 59,101 total)
vasimihalca (3/8/2009)
This is my first post on this forum, and I have a little problem at work that I don`t know how to resolve it.
I have experience on writing...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 8, 2009 at 9:23 am
Heh... That's not actually a BCP error... I'm pretty sure that the JPCFHONYVLDATA database doesn't actually have a copy of xp_CmdShell in it. The following command...
[font="Arial Black"]EXEC [highlight="YELLOW"]JPCFHONYVLDATA..[/highlight]xp_cmdshell @bcpCommand[/font]
......
--Jeff Moden
Change is inevitable... Change for the better is not.
March 8, 2009 at 9:18 am
GilaMonster (3/8/2009)
Jeff Moden (3/7/2009)
Consider the OP in the following... Lynn may have competition for saint-hood... 🙂http://www.sqlservercentral.com/Forums/Topic670491-338-1.aspx
Mike is one of those people on my blacklist, due to his repeated demonstrations that...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 8, 2009 at 8:51 am
musheik (3/8/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 8, 2009 at 8:43 am
nelson.ahrens (3/6/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 7, 2009 at 9:23 pm
Ummmm.... if they don't have sensitive information in them, why would someone encrypt them? Also, if you really need to have them decrypted, see the person with the encryption...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 7, 2009 at 9:18 pm
RBarryYoung (3/7/2009)
Jeff Moden (3/7/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 7, 2009 at 9:13 pm
Heh... it's obvious that a lot of the articles on other sites, including SQL Mag, aren't deeply reviewed for technical content either. Some of those articles are nothing more...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 7, 2009 at 6:12 pm
Not my job to judge, but "Well Done!", Flo. 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
March 7, 2009 at 3:46 pm
Consider the OP in the following... Lynn may have competition for saint-hood... 🙂
http://www.sqlservercentral.com/Forums/Topic670491-338-1.aspx
--Jeff Moden
Change is inevitable... Change for the better is not.
March 7, 2009 at 3:43 pm
Gift Peddie (3/7/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 7, 2009 at 3:32 pm
Gosh, I don't know how to build a policy. But, as a side bar, I'd never use a policy that forced any object name to use a prefix such...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 7, 2009 at 3:29 pm
That's the first time I've heard of someone writing a CLR stored procedure and I'm curious... what does it do?
--Jeff Moden
Change is inevitable... Change for the better is not.
March 7, 2009 at 3:19 pm
I'd recommend that you never import 3rd party directly to permanent tables. I always do the imports to temporary staging tables so I can validate the data as being...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 7, 2009 at 3:17 pm
Gift Peddie (3/7/2009)
The link below says Trace Flag 1118 is not really needed in SQL Server 2005 and above because of changes made. The user is supposed do...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 7, 2009 at 3:13 pm
Viewing 15 posts - 44,731 through 44,745 (of 59,101 total)