April 23, 2012 at 11:31 am
hi everybody
i have table with 45 field.if i want break it in two or three table. i will face problems in working with this table (inserting,updating,deleting,searching with hard query).is there any must that i should break table into deferent table?
almost all table data type are int and i write it with win application and i will use it in small network.
.net 3.5 and sql 2008
April 23, 2012 at 11:54 am
Hi there,
My initial question would be why do you need to break the table up? 45 columns is well within the limits of SQL Server 2008.
My recommendation would be to use stored procedures within the database to handle the selects, inserts, updates and deletes which in turn your .NET application will reference. If the structure of the table changes in future, you will only need to update the stored procedures and not the .NET application.
:exclamation: "Be brave. Take risks. Nothing can substitute experience." :exclamation:
April 23, 2012 at 11:58 am
vahid.arr (4/23/2012)
hi everybodyi have table with 45 field.if i want break it in two or three table. i will face problems in working with this table (inserting,updating,deleting,searching with hard query).is there any must that i should break table into deferent table?
almost all table data type are int and i write it with win application and i will use it in small network.
.net 3.5 and sql 2008
Unless the data is not normalized and hard to work with, why split it up?
So...
1. Is the data in this table normalized? (If it is, leave it)
2. If the data is not normalized, figure out how many tables you need to logically store your data in a normalized fashion.
Jared
CE - Microsoft
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply