Viewing 15 posts - 44,716 through 44,730 (of 59,095 total)
The "+1100" indicates the time zone of the date. You may have to substract that as a number of hours and minutes from the date and that will give...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 8, 2009 at 6:28 pm
IF EXISTS(Select 1 from t_Names where id = 1234)
BEGIN
Select isNull(fName, 'N/A') from t_Names where id = 1234
END
ELSE
BEGIN
...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 8, 2009 at 6:22 pm
Heh... in cases like this, I believe that being cynical is a healthy thing to do.
I wouldn't isolate the converstation nor the requirements to just the DBA... there may be...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 8, 2009 at 6:19 pm
Jeffrey Williams (3/8/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 8, 2009 at 6:07 pm
radek (3/8/2009)
I read something about indexes, that indexes is good create in "big table"
But when I create table in MS SQL by GUI and...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 8, 2009 at 6:03 pm
I agree, Flo... I just want to make sure what the OP means by "Deleted"... sometimes folks just mean "not included in the result set" and I wanted to be...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 8, 2009 at 5:16 pm
Those would certainly qualify as "housekeeping" stored procedures. I'm curious... why the question?
--Jeff Moden
Change is inevitable... Change for the better is not.
March 8, 2009 at 10:02 am
Chris Morris (3/8/2009)
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...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 8, 2009 at 9:58 am
Heh... even after the typo was repaired, no one got the correct answer because it wasn't listed. The correct answer should be...
"Who cares? Rewrite the code to be...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 8, 2009 at 9:31 am
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
Viewing 15 posts - 44,716 through 44,730 (of 59,095 total)