'' would be character data so it would not be compatiable with datetime,.

SQL server uses 1 jan 1900 instead, various other systems use other dates to act as...

no not by default,

also this is the 2008 forum, in 2008 you can in 2000 you can't

the pros are that you will have a nice sequential index that will fill up without causing splits

the cons are that if on the off-chance two records get inserted...

you could seperate them into different queries, try and do the IFS in steps and save the results to a table in between steps.

might run a bit quicker...

That is the expected behaviour and follows the SQL ANSI standards on sub-selects.

It is strange but it is worth knowing as it catches people out.

more detail here

http://onlamp.com/pub/a/onlamp/2002/08/22/gennick.html

the max capacity for sql server can be found here

http://msdn.microsoft.com/en-us/library/ms143432.aspx

Temp Db is like any other so the max size as mentioned would be 524,272 terabytes.

However in practice it...

you wont be able to get that information by default sorry, you can build this functionality in with triggers however this will only help for the future.

why start a new topic and not follow up on the current one you have going?

http://www.sqlservercentral.com/Forums/Topic1010635-391-1.aspx

you can not get that information from sql, however you should base your index rebuilds based upon the current level of fragmentation rather than use the last date of rebuild.

SQL_1xCompat_CP850_CI_AS is an upgrade collation, so i would look at possibly changing this before you do the upgrade on live.

have a look at Ola's scripts they are all really good and there is one for index maintainence (IndexOptimize)

http://ola.hallengren.com/

You should really put your question in the text rather than in the heading,

however i would start by comparing the execution plans between the two servers

most likely the statistics...

from that error it seems like there is a difference in the collation between the servers that the upgrade can't handle, what collation are you running on the sql...

it looks like the meta-data is out of date, try clicking on the excel destination data flow to reset the meta-date

have you checked the error logs?

have a look as there will be a more detailed error message that will give you a clue on why the upgrade failed