I've got an Umbraco website (v4.0.3) running on VistaDB. The database currently is about 8 mb in size. This version of Umbraco seems slower than other Umbraco websites running on SQL Server. Can it be slower because of VistaDB? If it is I'd like to export my current version to SQL Server. Is there an easy way to do this because on http://www.vistadb.net/ it only talks about exporting VistaDB4 and not VistaDB3.
I think I read somewhere that making a package of your complete site, including content would work for migrating from vistadb to SQL. My brief encounters with VistaDB databases also seems to conclude that VistaDB is very slow.
I have read elsewhere that you can use the database migration tool from microsoft to do the transfer. The trick is use a developer license of vistadb to do the export.
It would also be worth checking the memory of your IIS workers, and of your server, as this is likely the main different between sql server and vista db. As VistaDB is in process, the full 8mb should be in memory for it - if your server is tight for memory, or your pools are recycling frequently, this could be causing the DB to get released too often. SQL Server holds onto the memory more aggressively, which might mask this issue slightly better. Also if your SQL server is on the same box as your IIS, you might want to stipulate server_max_memory in the server properties - this will prevent it from being over possessive of memory - which it can be.
VistaDB slow?
Hello,
I've got an Umbraco website (v4.0.3) running on VistaDB. The database currently is about 8 mb in size. This version of Umbraco seems slower than other Umbraco websites running on SQL Server. Can it be slower because of VistaDB? If it is I'd like to export my current version to SQL Server. Is there an easy way to do this because on http://www.vistadb.net/ it only talks about exporting VistaDB4 and not VistaDB3.
I think I read somewhere that making a package of your complete site, including content would work for migrating from vistadb to SQL. My brief encounters with VistaDB databases also seems to conclude that VistaDB is very slow.
Also check this thread for an alternative route, using umbImport.
I have read elsewhere that you can use the database migration tool from microsoft to do the transfer. The trick is use a developer license of vistadb to do the export.
VistaDB blog has a few options listed:
http://www.vistadb.net/blog/post/2008/03/28/Using-SqlBulkCopy-to-move-data-from-VistaDB-to-SQL-Server.aspx
http://www.vistadb.net/blog/post/2009/11/13/Using-SQL-Server-Integration-Services-to-Migration-VistaDB-4-Data.aspx
http://www.vistadb.net/blog/post/2009/11/13/Using-SQL-Server-Import-and-Export-Wizard-with-VistaDB.aspx
It would also be worth checking the memory of your IIS workers, and of your server, as this is likely the main different between sql server and vista db. As VistaDB is in process, the full 8mb should be in memory for it - if your server is tight for memory, or your pools are recycling frequently, this could be causing the DB to get released too often. SQL Server holds onto the memory more aggressively, which might mask this issue slightly better. Also if your SQL server is on the same box as your IIS, you might want to stipulate server_max_memory in the server properties - this will prevent it from being over possessive of memory - which it can be.
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.