How many objects

  • Has anybody worked with SQLServer creating every month 100 tables and 200 new views, would it will work correctly?

    Thanks for advance

  • I forget but there is a maximum number of tables and views that can exist. Also this would be a nightmare to admin so I will never try personally. However as to if it will work, yes.

    "Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)

  • Thanks, for the answer. I am using all of this tables becouse they are controled on the same object, they are all the same structure but different names, then it will be easier to take control on them.

  • I went down this route with one of our developers here and we decided to make a compromise that you might want to consider for the shear impact of admin. Since the structure is the same, if possible (this is what we did) add a new column to one of the tables and make as part of the primary this new column. What you do on the column is the name you would have normally have given the table, thus allowing you to have just one table (or a few depending on the amount of data) that you can still identify the records for seperate sets. I know there are some cases where this is not feasable but a large number of tables can get to be a headache when problems arise.

    "Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)

  • Well let me explain my problem.

    I have to receive data form various stores, the database have to handle sales, storage and manufacturing. SaleItems Table will grow more than 1,5 million lines a month, the other ones may grow less but almost 0,5 million lines.

    I find 2 solutions:

    1-All Tables and stored procedures in same database total 30 tables, about 70 Stored Proc.

    2-Generate 30 new tables and their stored procedures(with their names) evary month and put all new data. (all same structure but different names including year and month). My problem is not administering Database. the problem will come if it will be problems when having more 1000 tables on the database, or If there is not any problen for SQL server to manage 1,5 million lines a month on the same database. I thought if i keep separate sored procedures for every month I can get speed improvments on SQL Question to the database.

  • If you build normalized structures and run adequate hardware speed will never be an issue in my experience. I'd go with option number one for sure.

    Andy

  • Thanks I will then go for first solution.

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply