sure, this is a good way too... Thanks both for your quick help.

Yes this will help, ... I'll have to apply few more filters to restrict the result to desired columns and will be done... Thanks...

Yes it works... thanks Eric...

Thanks Eric...

I created a database with two file groups, primary(default) and secondary and then creating following table.

CREATE TABLE [dbo].[TestTable]( [ID] [int] NOT NULL,

[Line] [smallint] NOT NULL, ...

Actually I found this...thanks

Thanks Dan...

so we just use with collate clause with whatever collation we want in the Create Database syntax right?

apart from above reply,

If those few million rows were inserted separately later, then the database mdf size might have grown to more extent for that operation and then probably backup...

read this article, it has detailed information about partitioning.

Thanks for the info John,

I am not partitioning the table and creating any partition function and range etc. All I am doing is just separating data from one HUGE...

Thanks Perry...

Is it possible to partition a large table with billions of rows into separate databases and not in different file groups with the same process I mentioned above. Can...

I am aware of table partitioning where we create partition function, partition scheme and then separating the records in different filegroups based on the boundry values defined in partition function....

Thanks Vidya...

So, what other ways are there for Horizontal Partitioning apart from table partitioning?

Okay, let me see what I can do here... Thanks everyone for the help...

Thanks Vidya and Lowell for your quick replies.

Due to complexity of the update operation, I am not able to split them in batches. will it be a good option if...

would this work?

exec sp_msforeachtable "select * from ? where TestId = 100"