It should not matter if you are on a cluster or not. ...

I believe your issue is that you have a lower case "s" instead of an upper case "S"

try doing

sqlcmd -S servername i- filename

instead of

sqlcmd -s servername i- filename

-S is...

Seems like you have something strange happening here.

I run the following code

create table floattest (id int identity(1,1), flval float)

insert into floattest

select flval from (Values (36.8413614879047), (16.094379124341), (6.23832462503951),

(27.6310211159286), (18.4206807439524),...

I definitely tend to agree with Ed and George on this one. I would personally prefer to stay as current with the technology as humanly possible when given the...

That is correct. As long as you are not distributing transactions...

Any possibility of two different table structures that you could bring together through views?

Or perhaps you could create your own hierarchy structure that essentially works in the...

Moving a package from a SQL 2000 over to a SQL 2005 server will definitely not create a job for you to run that package. That is something you...

I honestly have no idea what the thought process was behind this.

However, I suppose it is logical that since the Constraint exists on the table that the data would have...

A global (##) temp table can be dropped from any connection (not just the one that created it). A regular (#) temp table is tied to the connection...

I may be misunderstanding the question but if you are trying to get rid of a global temp table that should be as easy as find the table name

(select...

Your problem here is that the row that is causing it to fail is the row you are adding on the insert (it inserts, then checks so it will fail...

Based on the script you have here, it does not look like you have the tail of the transaction log backed up and that seems to be causing the problem....

If you want to load data from a SQL 2000 into a SQL 2008 try using the SQL 2008 Import/Export tools instead. In just doing a quick test...

Stamey (2/19/2009)

---

You have a security problem, most likely, because SSRS in the Standard edition does have subscription capabilities. All I run here is Standard edition and I have subscriptions running...

This runs incredibly fast on my local machine as well (not remotely fast desktop).

I am guessing with 3500 DB's you may very well be having some contention issues on tempdb...