Author |
Topic |
|
pierretopping
Junior Member
United Kingdom
224 Posts |
Posted - 18 December 2008 : 07:27:12
|
Hello Everybody,
I’ve been running SNITZ with the standard access database for sometime now, and although performance is good, I’m aware that performance could be an issue, and indeed when users are using the search facility on the database disk access is high.
The database currently has 20’000 records, and is only around 25mb in size.
I’ve been thinking about moving the database file to a ramdisk to speed up performance, and simply setting up a job to automatically copy the database back to hard disk every 30 minutes or so in case of a system crash, and also to copy the database to harddrive on system shutdown.
I’ve been looking at the below, running on my Windows 2003 server: http://www.codeguru.com/cpp/w-p/system/devicedriverdevelopment/article.php/c5789/.
Has anybody else used a Ramdisk, or has anybody got any comments on it?
Thanks,
Pierre < |
|
AnonJr
Moderator
United States
5768 Posts |
Posted - 18 December 2008 : 07:42:00
|
You'd be far better off upgrading to MS SQL Server or MySQL as your bigger problems lie in the RDBMS's ability to handle concurrent requests and large data sets.< |
|
|
pierretopping
Junior Member
United Kingdom
224 Posts |
Posted - 18 December 2008 : 08:23:33
|
Thanks for the reply. Does anybody know if when you migrate from an access database to a MySQL solution, does the topic ID change of the topics ?
Our website news section has a lot of links into the snitz database, and I would hate to loose the links..
www.tredegar.co.uk/forum
< |
|
|
AnonJr
Moderator
United States
5768 Posts |
Posted - 18 December 2008 : 08:34:09
|
There's a guide or two floating around for upgrading to MySQL. The biggest thing is to make sure the Snitz code creates the tables first, then migrate the data. Trying to just blit the tables over has been the biggest source of problems for those upgrading.
While I don't want to dissuade the use of MySQL, I've noticed that trying to go from Access to MS SQL Server tends to be a little easier (though the same advice as above applies... let Snitz create the tables, then move the data). But that may just be me. < |
|
|
pierretopping
Junior Member
United Kingdom
224 Posts |
Posted - 18 December 2008 : 09:09:39
|
Thats great, thank you for your help :o)
Pierre< |
|
|
|
Topic |
|