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 |
|
jazzym
Yak Posting Veteran
94 Posts |
 Posted - 2002-01-21 : 10:28:56
|
| Hi,I have recently changed hosts (to my own housed server) and re-set-up my two web sites. Both use SQL Server 2000 and both use the same ODBC connection and same database. (table names are SITENAME_tablename)The site worked fine on the old server (also running SQL 2000 on NT4)It's now running on SQL 2000 on Win2k. (just to let you know)I get this error now on any time i ever try to insert a date or also the NOW() value in VBScript:-"The conversion of char data type to smalldatetime data type resulted in an out-of-range smalldatetime value."I never had this problem before. The only thing i can think it might be is that my SQL Server is set to English(US) but i cant find anywhere to change that property. The Win2k regional settings are English(UK). Is there any known bug, explanation for this? what might have changed between the two? If it is this region thing in SQL Server where can i change it?Any help greatfully apreciated! ThanxJazzyM |
|
|
Nazim
A custom title
1408 Posts |
Posted - 2002-01-21 : 10:33:25
|
| Have a look at Set DATEFORMAT in BOL. it will help you change the Datetime Settings.--------------------------------------------------------------Dont Tell God how big your Problem is , Tell the Problem how Big your God is |
 |
|
|
jazzym
Yak Posting Veteran
94 Posts |
Posted - 2002-01-21 : 12:46:36
|
| Tried and failed. Nothing seemed to change it. Besides how would that explain why the server is causing these errors when it's pretty much a default setup. That's what i dont understand. I dont remember anything in the installation process of SQL Server 2000 asking what region i wanted. I thought it would pick that from the regional settings of Win2k.Maybe it's worth me reinstalling again? |
|
|
|
izaltsman
A custom title
1139 Posts |
Posted - 2002-01-21 : 14:22:22
|
| I don't think this is a SQL Server-related problem. This has more to do with how Windows2k and IIS handle regional settings. We had a similar problem after upgrading to Win2k recently. Had to tweak one of the registry keys like so: HKEY_USERS\.DEFAULT\Control Panel\International\"sShortDate"="dd/MM/yyyy"-------------------If trainstation is a place where train stops, what's a workstation?Edited by - izaltsman on 01/21/2002 14:28:46 |
|
|
|
|
|
|
Date problem / regions problem perhaps