| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 1 year, 11 months |
| seen | Aug 18 '11 at 22:08 | |
| stats | profile views | 10 |
|
Aug 18 |
awarded | Supporter |
|
Aug 18 |
comment |
Suggestion for Large SQL Server Database Design Thanks for ur input. we've applied the design principles which you're referring but will work on indexing once the development part is complete. I guess for partitioning you need Enterprise license and we've Standard edition license at the moment. |
|
Aug 18 |
comment |
Suggestion for Large SQL Server Database Design btw design is almost final and we're using SSRS for reporting requirements and its work great but still we're fine tuning and giving performance boost before going into production. |
|
Aug 18 |
comment |
Suggestion for Large SQL Server Database Design Thanks martin for your input. Actually the db contain statistics and historic record about agriculture products. The growth is substantial and your input about backup is useful. We've already planned the backup routine and your input added some great value. Our existing backup process for different database has somewhat same approach. Daily differential and weekly full backup. |
|
Jun 1 |
comment |
Suggestion required for Large Database Optimization and performance thanks for your links. both links give some good technical inside. We can run statistics as schedule job but it would be helpful if you've any article for comparison about performance or stats. |
|
Jun 1 |
comment |
Suggestion required for Large Database Optimization and performance Column-store table is the new thing for me. Let me do some research on this. thnx anyway. btw we're using MS SQL server 2008 |
|
Jun 1 |
comment |
Suggestion for Bulk Data Import The application we're going to create is web based application where user have limited control over SQL server. User will upload the file through browser and rest of the operation will be done at server side. |
|
Jun 1 |
comment |
Suggestion for Bulk Data Import Actually we're creating web based application so we won't allow user to access database interface directly. Our application first import the file and then we do rest of the operation through our application. |
|
Jun 1 |
comment |
Suggestion for Bulk Data Import nvarchar is fine with us coz our database going to support multilingual attributes. I am reviewing the topis. thanx |
|
Jun 1 |
awarded | Student |
|
Jun 1 |
awarded | Editor |
|
Jun 1 |
revised |
Suggestion for Large SQL Server Database Design edited title |
|
Jun 1 |
asked | Suggestion for Bulk Data Import |
|
Jun 1 |
asked | Suggestion required for Large Database Optimization and performance |
|
Jun 1 |
asked | Suggestion for Large SQL Server Database Design |