Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
pandiarajan
Starting Member
1 Post |
 Posted - 2007-07-14 : 04:11:21
|
| Hi,We are developing products to target thousands of clients.Front-End : C#.Net 2005Back-End : SQL-Server 2005We started an Inventry control project (Product) with 10% percent of data as we didn't meet any clients (User requirements). I mean, I could not get complete user requirements. version by version, I need to change the database dynamically, and it should support backward compatiblity. While altering the database the existing primary keys are affecting. It seems I need to complete reconstruction of data Layer, Business Layer and Presentation Layer. How to avoid reconstructions in such scenerios? How database designers designing databases for a product like this? Or should I need to create "Table_Name_Serial_Number" (identity data type) column for each table and column to be primary key of that table?. Please help me!Thanks in advance,R. Pandiarajan. |
|
|
gvphubli
Yak Posting Veteran
54 Posts |
Posted - 2008-01-31 : 15:36:29
|
| first thing - without properly documented requirements you cannot design a product.second - you need to have a vision of next 2-3 releases.With all this you can design a database keeping some future scope in mind and have some extra columns here and there. Like what Micrsoft do in System databases, it leaves some coulmns as "reserved for system use".And databases CANNOT be designed dynamically on the fly. They usually have 1-2 yrs of life.And if you have to change the database design, then you have an effort to put-in to migrate data from previous version to new version, and thats how every one does.TechnologyYogihttp://gvphubli.blogspot.com/ |
 |
|
|
SusanthaB
Starting Member
14 Posts |
Posted - 2008-02-06 : 06:50:52
|
| I have a different opinion for this. When you want to do any alternations to database, table, function, stored procedure or data that could be achieved through T-SQL scripts. You have to write the scripts in such away to achieve your objective and you should have proper release notes describing how to release those patches. That’s how you do changes to databases. You got the point? |
|
|
|
|
|
|
|
|
how to design databases dynamically?