Viewing 15 posts - 31,336 through 31,350 (of 59,101 total)
SQL Kiwi (1/25/2012)
Jason Selburg (1/25/2012)
Yeah, that's what I meant Paul. 🙂:laugh: By the way, it's not often code produces a 'whoa!' reaction from me.
It wasn't a 'whoa' that came out...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 25, 2012 at 10:07 pm
This should do it, Chrissy...
DECLARE @SomeExampleDate DATETIME;
SELECT @SomeExampleDate = '01/01/2012';
SELECT STUFF(REPLACE('/'+CONVERT(CHAR(10),@SomeExampleDate,101),'/0','/'),1,1,'')
--Jeff Moden
Change is inevitable... Change for the better is not.
January 25, 2012 at 10:03 pm
umasingh (1/25/2012)
Chrissy321 (1/25/2012)
Hello All,How can I alter this convert statement to return 1/25/2012 rather than 01/25/2012.
Or return 1/1/2012 rather than 01/01/2012
SELECT CONVERT(varchar(10),getdate(),101)
Thanks if you can help.
This may help you.
Declare @x...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 25, 2012 at 10:02 pm
http://msdn.microsoft.com/en-us/library/ms190479.aspx
--Jeff Moden
Change is inevitable... Change for the better is not.
January 25, 2012 at 9:52 pm
Gosh... I check for "out of spec" indexes every night and either reorg or rebuild depending on how bad they may have gotten.
Shifting gears a bit... we had a similar...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 25, 2012 at 9:48 pm
kirkdm01 (1/25/2012)
I tried you're second approach and i get no results if i put in 13, 12 or 1
If you spell "Parameter" correctly :-P, Jason's code seems to do the...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 25, 2012 at 9:38 pm
Some systems terminate lines with CHAR(0), the NULL character... and that makes a hell of a mess in SSMS.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 25, 2012 at 9:11 pm
SQL Kiwi (1/25/2012)
Brandie Tarvin (1/25/2012)
Anyone can fly. You just throw yourself at the ground and miss.Been reading Douglas Adams recently, Brandie?
I never made my way all the way through it...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 25, 2012 at 8:21 pm
Heh... yeah. I should know better by now. Thanks, Paul.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 25, 2012 at 8:16 pm
Crud... I know what the problem is. Some folks at work decided that were going to use the 2008 client tools (including SSMS) on a 2k5 database. The...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 25, 2012 at 7:53 pm
apat (1/25/2012)
DECLARE @currentdate datetime
DECLARE @olddate datetime
set @currentdate = getdate()
set @olddate =...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 25, 2012 at 7:45 pm
shivaram challa (4/2/2009)
Krishna Potlakayala (3/26/2009) You would not be able to shrink the log file unless you truncate it. When the sys.databases "log_reuse_wait_dec" coulmn status is "LOG_BACKUP", then you should...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 25, 2012 at 7:37 pm
Steve Jones - SSC Editor (1/25/2012)
If you do #3, you will need application code changes to find the data that is moved.
Maybe not. You can use synonyms or "pass...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 25, 2012 at 7:30 pm
Hmmm... I wonder what they did from 2k5 to 2k8 because it used to be "guaranteed" as of 2k5. From the 2k5 BOL on the subject of DBCC UPDATEUSAGE...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 25, 2012 at 7:13 pm
@jack-2...
Congrats on the 10K milestone!
--Jeff Moden
Change is inevitable... Change for the better is not.
January 25, 2012 at 6:50 pm
Viewing 15 posts - 31,336 through 31,350 (of 59,101 total)