I am working on site in asp.net with c# and using database sql server 2000 and managing all the data on server i have created one database on server and in that i have created 15 table. should i continue with the same or create another database for table.
tell me how many tables should i maintain in one database. and what precausion should i take while mainting database to increse the speed of site.and what precausion should i take to avoid serverload
please guide me i dont have an idea.
thanks for spending ur valuable time for me.
I suppose that would depend on the database structure of your application. If your application required more tables i guess you create one in the existing database it self.
I dont think you need to worry much with only 15 tables in the database. Frankly your db can handle many tables still.... :) so chill
I would suggest create a unique db for each application. Again if there are very few tables in each application u can use the same database as well. There are many tweaks in the database than just the no. of tables to make it faster... so i will not consider more tables as a major problem for bad database perfomance.
|||
Sharvari:
I am working on site in asp.net with c# and using database sql server 2000 and managing all the data on server i have created one database on server and in that i have created 15 table. should i continue with the same or create another database for table.
You would generally create a new database for each individual application unless several applications may share the data.
tell me how many tables should i maintain in one database. and what precausion should i take while mainting database to increse the speed of site.and what precausion should i take to avoid serverload
There is no set limit that defines how many tables you should have. The important thing when it comes to database efficiency is the table design, adequate levels of normalisation, proper indexing, and write good optimised SQL for data retrieval.
|||
hi,
read this link this may be helpful to you.
http://publib.boulder.ibm.com/infocenter/db2luw/v9/index.jsp?topic=/com.ibm.db2.udb.admin.doc/doc/r0001029.htm
|||
i have created one database on server and in that i have created 15 table. should i continue with the same or create another database for table.
You can go on creatng as many tables/stored procedure/functions/views as you want in a database. There is indeed alimit of maximum number of objects that can be created in a database but don't worry you are far...far away from that.
what precausion should i take while mainting database to increse the speed of site.and what precausion should i take to avoid serverload
There are many techniques for better administration of SQL Server. Just try a google and you'll find so many informative and useful articles.
Do you mean that you will use stored procedure to get the data or use a table to get the data?
|||Well, I can't exactly understand what you are trying to ask. Anyways, I think you are trying to compare tables and stored procedures. But, tables and stored procedures have different objectives.
Tables are used to store the data in a database.
Stored Procedures are used to modify the data stored in the tables. By modify I mean Insert/Update/Delete the data.
So, basically both of these 2 have different purposes and there should be no comparison between these 2.
whats the effect on server by using table and whats the effect on server by using store procedure which is more convinient. thanks for spending ur valuable time for me.
As mentioned, tables are where you store the data. Stored procedures provide a mechanism which allows you to encapsulate logic into a unit which can be re-used. Therefore a stored procedure can contain logic on how to select/update/delete data and various other things.
No comments:
Post a Comment