Different regional settings discovered in SQL cluster nodes!

We have advertantly failed to verify correct regional settings on both (Win2
003) Cluster nodes prior to installing SQL Server 2000 Ent Ed. SQL Server is
installed in an Active Passive config with System Databases installed to a
shared disk (Drive G Nod
e 1 has US English regional setings (date = mm/dd/yyyy) and US English input
Locale
Node 2 has Australian English regional (date=dd/mm/yyyy) and US English inpu
t locale
Our (mission critical production) database was detached from its old server
(AustralianEnglish regional and US English Locale) and moved to this clust
er 2 days ago. Testing and failovers work fine and the solution went live. W
e have only just discovered
the date discrapency. As the current date is (day & month) is still below 13
, nothing has blown up yet but we are 2 days away from the 13th!
The sysadmins are content to change the regional settings on node 1 to Engli
sh Australian and leave it like that. They failed-over the SQLService over t
o the second node and have scanned the systems databases and tables for date
s showing abnormal (future)
dates and found nothing. They believe there will not be a problem in simply
changing over Node 1's date settings to English Aust.
Sorry for the long note but I need to describe this as clearly as possible.
I am concerned that we have overlooked something. Can anyone tell me if it i
s safe to just change the system regional settings to English Australian? Wi
ll SQL server cope with the
date format change past 13Feb 13/2/2004 in AustEnglish format (dd/mm/yyyy)?
Should we rebuild the node with the correct regional settings and reinstall
SQL server on it? (In order to do this, SQL Server will need to be uninstall
ed from both nodes and the
master db deleted as the master db was created via node 1 US English to star
t with).
Thanks.
NRAs long as you have changed regional settings and you do not have code that
uses set dateformat otherwise this willbe ok. No datetime issues will be exp
erienced thereafter.|||Thanks for your reply, Olu. We did the change but found that SQLServer still
had problems on that node, and this was after we also fixed up the user pro
files to ensure the regional settings were correctly set.
We are attempting tonight to uninstall SQL reinstall, this time from the sec
ond node which was initially set with EngAust regional settings. We'll know
soon if that worked.
NR|||NR can U please keep me posted . . and what errors did you get on the node
after U changed regional settings'