What to use when creating reporting tables at Sql Server 2008 as a scheduled task -

i want create database tables reporting purposes.as seperating reporting system transactional system.

i create tables

• .report_company_id_12_unique_views (use case 1)
• .report_company_id_18_unique_views
• .report_adserver_id_22_unique_counts (use case 2)
• .report_adserver_id_44_unique_counts...so on

we have 50+ reporting use-cases , tables hold no more 200 rows , have deal every use case differently unique.

but have around 8.000 tables these purposes.

8.000 tables don't sound cool wanna use reporting db fast access.

this db designed datastore....even there no primary keys in tables....all purpose read access data extracted n* million row tables.think denormalized version of real db reporting.we create tables ,insert data , next schedule drop , insert data again.

my question tool should use scheduled task ?

• 1.sql agent(where have write cursors in process)
• 2.windows task library can call code , let out of process classes job.
• 3.???? ( other choice )

-nosql solutions not accepted. :(

my requirements meet

• 1.easy debug ( relatively )
• 2.easy extend ( relatively )
• 3.easy deploy ( absolutely )

antinescience

i agree, first response should "refactor you're not using 8000 tables". can fast, read-only access primary keys. there's no need kind of table bloat - if you're going that's basic key-value store, nosql alternative. – antinescience 17 hours ago