Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2006-12-22 : 07:46:07
|
| Sharon writes "Hi - I asked earlier why character aa/bb/cccc fields are being implicitly converted to dates in QA as dd/mm/yyyy, but when the statement is run as isql/osql via xp_cmdshell, they're being seen as mm/dd/yyyy.I have a workaround to re-set the time on GETDATE() to midnight, which solves my immediate problem in using GETDATE() as start/end comparison to a db that only ever stores times as midnight. While that does solve my immediate reporting need, I'm still interested to know why xp_cmdshell is using a date format default that Query Analyzer isn't. I'm concerned that this issue will cause other problems because we just don't ever want character dates to be assumed to be mm/dd.Any ideas on where that pesky setting is? Thanks, Sharon." |
|
|
SwePeso
Patron Saint of Lost Yaks
30421 Posts |
|
|
|
|
|
date format default for xp_cmdshell 