Creating temporary table using a template table dynamically

I'm having an application for users to extract data from sql 2K. Problem is that I need to split the huge amount of data into few pages on the application screen.

Since my order by clause could be dynamic, which is a big problem, the solution I can think of is to populate a temporary table ( within a stored proc ) and assign a column within the temporary table with a running number.

This stored proc would accept among them, an argument, which is the table name of a base table.

However, I would like to create this stored proc in such a way that I could create a temporary table based on given based table name, complete with the field sizes and types. On top of that, would like to add a new column to this temp table to store a running number key.

Opinions appreciated. :)Refer to this linkSQL Performance (http://www.sql-server-performance.com/rd_temp_tables.asp) for information.

Creating stored procs that need to continusiouly append to a new table (this is to scrub d

I have 1 table with a huge amount of data that I recive from someone else in a flat file format. I want to be able to filter through that data and scrub it and find out the good data and bad data from it.

I'm scrubbing the data using different stored procs that i've created and through a web interface that the user can pick which records they wish to create.

If I were to create a new table for clean records, what is the syntax to keep Appending to that table through the data that i'm obtainig via the stored procs that i've created.

Any thoughts or suggestions are greatly appriciated in advance

Thanks again in advance
RBCheck outINSERT (INTO)

Or you might consider adding a STATUS column and flagging all records initially as BAD and then flagging with GOOD as appropriate as you progress through your scrubbing routines.

Terri

Creating custom merge profile

You can also in the Create Publication Wizard, select
Yes, minimize the amount of data on the Optimize
Synchronization page (@.keep_partition_changes = true),
and consider if column-level tracking is appropriate for
the business needs.
The timeout parameterss are usually adjusted only when
timeouts are an issue, and won't optimize your process.
You might want to look at this article to get more info
on Optimization:
http://www.microsoft.com/technet/pro.../sql/2000/main
tain/mergperf.mspx
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
Hi Paul,
thanks a lot.
Janez