My view on the case is log shipping. Although it is an enterprise option, it can be done manually (script to auto) in other version.

Transaction log replication is more on...

If backup view maintenance plan, it is in one of options.

Dynamic sql can help you.

What about two RefID in table1, which one to pick up?

Try to recompile the sp. It could be result of old execution plan

Check registry entry

HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL Server\80\Tools\SQL Query Analyzer\Options\GeneralTab\TemplatesPath

It should have the path information.

Use convert to truncate.

It may stand on nonclustered primary key.

use pubs

go

alter proc sp1 as

select * from #te456 where state = 'ca'

go

create proc sp2 as

select * into #te456 from authors

exec sp1

drop table #te456

go

exec sp2

This means the data already has quality problem.

You can still add constraint by

alter table Appointment WITH NOCHECK add constraint FK_Appointment_ApptProcDetail foreign key (AppointmentID) references ApptProcDetail(AppointmentID)

try

User Id = sa

leave Password as blank.

Add check constraint on smaller tables will help optimizer to search.

I had similar experience. It was related to some kind memory thresh in ODBC driver.

You may check by selecting smaller table to verify.

Every row in tbl_Tracking will scan through Acct_Stats. thus

8 million * 3 million at least.

Not to mention distint's impact.

Corellated join is an option.

Enterprise manager Generate SQL Script is an option.