Perhaps you could add an extra field to the table you are inserting into - call it BatchID or something similar - then you just need to work out how...

Have you tried running in debug to try and isolate exactly when the error appears?

As you can see from Chris' example, the subquery cannot execute without the parent query - this is what 'corelated' refers to.

An independent subquery can run in isolation, eg

select *...

How are you loading the data at the moment?

1.5GB every two hours is lots less than 150GB a day - I don't understand!

Does the data need to be available to...

Please do not submit the same post in multiple forums - follow this link to see my suggested approach, which expands a little on Andy's.

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=9&messageid=225706

This is fairly straightforward.  You do not need separate databases for this information, even if the number of schools gets very large - you will find that having everything in...

Please do not submit the same post in multiple forums.

Use this link for answers to this question:

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=7&messageid=225720

This isn't very elegant but it works.  You'll notice that the calculation of @totalmins at the end relies on integer division - related to the MOD function that you are...

Try this - untested, but should get you going:

select r1.*

from server1.database1.information_schema.routines r1

left join server2.database2.information_schema.routines r2

on r1.routine_name = r2.routine_name and r1.routine_type = r2.routine_type

where r1.routine_type = 'procedure' and (r2.routine_name is null)

Why not just detach the dbs on the old computer, copy them across using Explorer and then attach on the new PC?  This takes SQL Server out of the equation.

Also,...

Using EM to input data, CTRL/0 will enter a NULL for you.

If you are really concerned, I guess you could write a trigger that will always convert space to NULL,...

SQL Server recognises a space as being different from a null (because it is).  Why don't you just configure your app to convert a space to a null and write...

Can't find a way of doing this without using sysfiles - here's an example, if you need it:

declare @dbname varchar(100)

declare @strSQL nvarchar(500)

set @dbname = 'master'

set @strSQL = 'select name, fileid,...

What you are trying to do is a little more complex than this - though this gets a bit closer, I think:

declare @table varchar(50)

declare @str1 nvarchar(1000)

set @table = 'test_table'

set @str1...

I've never seen this message before - you've got something strange happening there!  All I can suggest is that you remove transformations one at a time and keep trying ......