What's your suggestion ?
-
Hi experts. I wanna create a Win App that needs a simple database, just for saving plain text and plain numbers. Now i don't know which one is better ! sdf Database , or mdf database or XML. What's your suggest ? Could u guide me ? Thank you.
-
Hi experts. I wanna create a Win App that needs a simple database, just for saving plain text and plain numbers. Now i don't know which one is better ! sdf Database , or mdf database or XML. What's your suggest ? Could u guide me ? Thank you.
DB4O
-
Hi experts. I wanna create a Win App that needs a simple database, just for saving plain text and plain numbers. Now i don't know which one is better ! sdf Database , or mdf database or XML. What's your suggest ? Could u guide me ? Thank you.
-
Hi experts. I wanna create a Win App that needs a simple database, just for saving plain text and plain numbers. Now i don't know which one is better ! sdf Database , or mdf database or XML. What's your suggest ? Could u guide me ? Thank you.
This is really a matter of opinion, so here's mine: - for single user application with small amount of local data => SQL Server Compact Edition - for multi user application with medium amount of shared data => SQL Server Express / Oracle XE - for multi user application with large amount of shared data => SQL Server Std or Enterprise / Oracle 11g I believe that the next question you would have is: what is a small or large amount of data. Again a matter of opinion but perhaps some quantities (these are certainly not accurate but give some idea): - small amount could be less than 1 GB, perhaps less than a hundred tables and no table contain over 10 000 rows - large amount could be more than 4 GB of actual data, perhaps 500+ tables tables and and some tables contain over 10 000 000 rows. User amount is high, let's say over 1000 concurrent. I already regret that I wrote any quantítative information since it's really not that simple (also consider licensing, support level, activity levels, transaction counts etc.) but I'm prepared to get flamed :)
The need to optimize rises from a bad design.My articles[^]
-
This is really a matter of opinion, so here's mine: - for single user application with small amount of local data => SQL Server Compact Edition - for multi user application with medium amount of shared data => SQL Server Express / Oracle XE - for multi user application with large amount of shared data => SQL Server Std or Enterprise / Oracle 11g I believe that the next question you would have is: what is a small or large amount of data. Again a matter of opinion but perhaps some quantities (these are certainly not accurate but give some idea): - small amount could be less than 1 GB, perhaps less than a hundred tables and no table contain over 10 000 rows - large amount could be more than 4 GB of actual data, perhaps 500+ tables tables and and some tables contain over 10 000 000 rows. User amount is high, let's say over 1000 concurrent. I already regret that I wrote any quantítative information since it's really not that simple (also consider licensing, support level, activity levels, transaction counts etc.) but I'm prepared to get flamed :)
The need to optimize rises from a bad design.My articles[^]
Nice response , thanks
-
Nice response , thanks