To end up with data in different files, you will need to do some sort of data transfer process. Either DTS or BCP will suit your needs.

Another option is to...

Sounds like you'd be better off using replication. Have a look at transactional publications with updating subscriptions.

Check http://www.sqldts.com. They'll have an example of checking for the existence of the file.

Isn't that what I said 😉

George, given that this is a SQL 2005 forum, I'd assume that Graham is using SQL 2005. If that is the case, then the fulltext catalogs are included in the...

With more relevant field names we can get an idea of what sort of data is stored in them.

One thing I see a lot of is duplicate address fields for...

Check http://www.sqldts.com, I'm sure they have an example there.

Ok that right there is going to give you a very large bottleneck.

I'm betting your Page Life Expectancy is less than...

:w00t::sick::unsure:

Presuming the field names have been changed to protect the innocent, how about posting something a little less generic and we might be able to steer you towards a better...

Yes, Jeff does make assumptions, but they are the correct assumptions to make.

Blindly following a statement like "whatever you do, don't include the time components of the dates" doesn't make...

Yes the log shipping backups will contain all the data/schema affected by DDL and DML actions. It's just like a regular backup.

This can be easily and quickly simulated by setting...

Also, how big are the databases involved in the ETL process?

Anything over 2GB and you'll definitely have an I/O bottleneck. Another design issue that the architect should have planned for...

Do you need to drop all the indexes and re-create them? Have you run though a test scenario with at...

If they are all pointing to the same database, then a likely reason is parallelism. A connection can only be used by one task at a time. If you have...

Ok, if 'C:\Documents and Settings\Admin\Local Settings\Temp\SQL.txt' is the file name then it's nothing to do with SQL Server.

Its the log file created by an ODBC datasource.

Check this,

http://support.microsoft.com/kb/268591