Minimum Date in DateStamp field is not 1-Jan-100 (Silly by SQLServer guys)

Minimum Date in DateStamp field is not 1-Jan-100. Wouldn't we expect that.
In SQLServer2000 is it "1-Jan-100", if not WHY ??,
In the previous versions it is "01-Jan-1753"
bikramjeetThe problem lies with the Gregorian calendar, not the SQL software.

If you go back before 1753, you start to run into all kinds of problems with dates. Finding out which day corresponds to a particular date means that the algorithm needs to know where you want the date resolved from a political standpoint as well as a chronological standpoint. There are also a number of other problems that crop up, such as certain calender days occuring more than once. It gets ugly.

See Wolfram (http://scienceworld.wolfram.com/astronomy/GregorianCalendar.html) for more explaination.

-PatP|||The problem lies with the Gregorian calendar, not the SQL software.

If you go back before 1753, you start to run into all kinds of problems with dates. Finding out which day corresponds to a particular date means that the algorithm needs to know where you want the date resolved from a political standpoint as well as a chronological standpoint. There are also a number of other problems that crop up, such as certain calender days occuring more than once. It gets ugly.

See Wolfram (http://scienceworld.wolfram.com/astronomy/GregorianCalendar.html) for more explaination.

-PatP

I always found that to be a lame excuse...

As if there aren't enough...what the technical word they use...oh well, kludges in M$ internal code anyway...

If they really wanted to..(and who the hell said ancient dates are precise anyway)...bulid it in tho the damn date functions...why limit it?

Next they'll be telling us you can't travel fatser than the speed of light...

The Church of M$|||I always found that to be a lame excuse...Yeah, but Convert() would be kind of funky if it had arguments for your location, political affiliation, and religion!

Oracle solves this problem by simply ignoring the Gregorian reformation altogether... You simply learn to live on Oracle time!

There are other client programming languages that have library code that detects the PC's locale and uses that to make the decisions (which are frequently incorrect) about date conversions. This can be a real hoot to debug, since the exact same binary running on the exact same release of windoze would change its results based on where it thought the PC was!

That leads to the issue of lunar calendars that have leap months added on a tough to predict basis... That's even more fun!

I don't remember if you were involved in the discussion of database normalization that Rudy invited me to that was the first time I'd posted here... The issue of dates is a lot like the issue of normalization: if you know nothing about it, no problem; if you know a little bit about it, not a big problem; as you learn more than just a little, the problem gets bigger and uglier really fast. The whole thing becomes a slippery slope, so it gets tough to dance!

-PatP

migration sql Server 2000 to sqlServer2005

hi,

i must convert my SqlServer2000 to SqlServer2005. I just do it on my Computer and i run a component "SQL Server upgrade wizard" it convert my SQLServer.
But now i must do it on my Server Web and if i run that component it give me an error : "must run SQL 6.5" and i don't installed it.

Can i download it with all right migration?

thank you

If you get such error you may have inherited a database upgraded from 6.5 to 2000 with a wizard that could be a problem because I always advice 6.5 migration should be manual done by a skilled SQL Server expert. So create a blank database and run the SSIS(sql server integration services) and the error will go away. Hope this helps.

Migrating to Internationalized Datatypes

Hi,
Can anyone tell me how can I move my existing datatypes to
Internationalized datatypes in SqlServer2000. i.e
CHAR to NCHAR
VARCHAR to NVARCHAR
TEXT to NTEXT
I am facing two Problems when I use Alter table Command to Modify the Column
Datatype.
1)
When I try to alter CHAR Column to NCHAR that has Index Defined, SQL
Server gives an error ( Alter Column failed because One or more Objects
access this column )
I tried by disabling the constraints on the table, but that also did not hel
p.
2) Conversion From TEXT to NTEXT seems to be Unsupported . On Alter of
text Column Error comes, Cannot alter column because it is 'text'
Thanks,
AnujHi
I would create an identical table in the DB with the new table structure.
Then use SELECT/INSERT statements to copy the data over, or use DTS to map
the columns and then let DTS copy the data over.
Rename the original table and then re-name the new table to the original
table.
Re-create all constraints, Clustered Indexes and other indexes.
In-place changes will cause a lot of data movement, pages splits and updates
to indexes, making it a slow process. As the same time, with doing the copy
to a new table, you can first verify that everything looks good before you
proceed with re-naming tables.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Anuj Gupta" <Anuj Gupta@.discussions.microsoft.com> wrote in message
news:3076DEC3-4E4A-4873-96F8-692D4D335E05@.microsoft.com...
> Hi,
> Can anyone tell me how can I move my existing datatypes to
> Internationalized datatypes in SqlServer2000. i.e
> CHAR to NCHAR
> VARCHAR to NVARCHAR
> TEXT to NTEXT
> I am facing two Problems when I use Alter table Command to Modify the
Column
> Datatype.
> 1)
> When I try to alter CHAR Column to NCHAR that has Index Defined, SQL
> Server gives an error ( Alter Column failed because One or more Objects
> access this column )
> I tried by disabling the constraints on the table, but that also did not
help.
> 2) Conversion From TEXT to NTEXT seems to be Unsupported . On Alter of
> text Column Error comes, Cannot alter column because it is 'text'
> Thanks,
> Anuj