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 |
|
indersshekhawat
Starting Member
26 Posts |
 Posted - 2008-03-24 : 02:41:42
|
| I have a large database(sql2000). reports and data entry is going slow. I decide to make a copy of database and transfer all old data to another database . if user want report from old database he log on in old software. Is this is a right way to handle a large database (2GB) |
|
|
mfemenel
Professor Frink
1421 Posts |
Posted - 2008-03-24 : 10:02:30
|
| I think you're still going to have issues with data entry going slowly. SQL Server can easily handle a 2 GB database. I think you more likely have an issue in your design of the application they're using to enter the data or in your db itself. SQL server can scale way up over a terabyte without issue. I'd do some more investigating before assuming moving the data off will cure the problem.Mike"oh, that monkey is going to pay" |
 |
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2008-03-24 : 21:58:48
|
| 2gb db is small, what you need to do is rebuild index I believe. How often do you rebuild index or update statistics by the way? |
|
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2008-03-24 : 23:03:52
|
| We have database size upto 2.5 TB. 2GB is smallest database. you need to create maintenance plan as Rmaio has suggested. |
|
|
|
|
|
|
Tranfer data is right way ?