Will this work?

SELECT

s.ID,

s.M_ID,

s.T_Name,...

Since one of the tables will be dropped, I've decided to use

IF OBJECT_ID (N'dbo.tableA') IS NOT NULL

/*

--run code here to

exec usp_B to create my tableB add all data and...

Paul White( wrote

USE tempdb;

GO

CREATE TABLE dbo.A (a INT NOT NULL);

CREATE TABLE dbo.B (b INT NOT NULL, c INT NOT NULL);

GO

INSERT dbo.A (a) VALUES (1);

INSERT dbo.B (b,...

Jeff Moden (7/04/2010)

There's still a way even in SQL Server 2000. Long before synonyms, we used "pass through views" which are nothing more than a view that does a select...

Hi,

Jeff Moden(06 April 2010)

For the maximum speed, though, I'd maintain "two" main tables. One would be "online" and have a synonym pointed to it and the other one would be...

repeat post mistake

First, thanks folks for the great responses.

Rob Schripsema wrote

If you're talking about a non-clustered index, I think I would drop the index after truncating the table, then import the new...

Hi Bhuvnesh, Thanks for responding

you wrote:

The indexes will help on main table in reportting so rebuilding can be done after importing

but why do you want to rebuild indexes after...

Cheers for the responses folks

Thanks Jeff

Yeah, that's fair enough... Once I've got enough info and still believe I need help I'll post all the info necessary to receive help.

Cheers

Thanks for the response Jeff.

I take it when you mean not doing it all in one, but do it in batches within one job?

Edit:

Actually, about pre-aggregating, I'm a little confused...

Thanks Arjun, this advice will help with implementation.

Cheers