Lots of tables - this is unconventional. but will it be ok?

[ptj]

For a variety of reasons because of the way I need to access some data it would make my life much easier to create a new table for each 'job' on a database. The job will stay live for about 3yrs and then summary information will be archived, and the job table destroyed. I anticipate about 50 such jobs on the go at any one time, so 50 job tables.

Although this isn't normal practice, it would save me lots of coding - are there any good reasons I can't do it this way, and if I go ahead do I need to run some special SQL commands to make SQL server optimize itself?

Thanks

Phil.

 

[tlbroadbent]

SQL Server should have no problem with the structure. Simply make sure the tables are indexed and the data types are correct. Terry L. Broadbent - DBA
Computing Links:

http://tlbroadbent.home.attbi.com/prog.htm

faq183-874 contains "Suggestions for Getting Quick and Appropriate Answers" to your questions in the SQL Server forum. Many of the ideas apply to all forums.