Developer forum

No, there are no such plans at the moment. On this page http://documentation.dynamicweb.dk/Installation-23324.aspx you'll find the document 8001 and 8011 both containg suggestion on scaling hosting environment and choice of database in serveral scenarios.

The call to the access database in Application folder is to the Language.mdb which contains translations for the Admin user interface. When running on a 64 bit server this is no longer possible, so you'll have to switch to SQL.

If you're running a local solution or an externally hosted solution, there's no problem using SQL Server Express rather than Access.

Hi Jais

The maximum connections/users on the same solution depends on the hosting platform beneath. We have customers with websites that easily serves up to 50.000 sessions a day, on a SQL-Server based solution of course. This number can go a lot higher if needed.

Its true that an Access based Dynamicweb will run in to trouble with a lot of concurrent users - how many it can take depends on which modules are used etc. I've seen a solution taking more than 12.000 sessions a day in shared environment on Access - a bad idea, but its feasable.

You mention that there is a lot of calls to /admin/Language.mdb? I would like to know more about that if thats true. Because Dynamicweb should only make one connection to that database on login - and thats it.

In control panel under statistics you can fully deactivate the statistics collection for performance improvements.

If you have a project that requires a lot of sessions and need to discuss hosting, feel free to contact me or Hostnordic.

np wrote:

Hi Jais

 

The maximum connections/users on the same solution depends on the hosting platform beneath. We have customers with websites that easily serves up to 50.000 sessions a day, on a SQL-Server based solution of course. This number can go a lot higher if needed.

 

Its true that an Access based Dynamicweb will run in to trouble with a lot of concurrent users - how many it can take depends on which modules are used etc. I've seen a solution taking more than 12.000 sessions a day in shared environment on Access - a bad idea, but its feasable.

 

You mention that there is a lot of calls to /admin/Language.mdb? I would like to know more about that if thats true. Because Dynamicweb should only make one connection to that database on login - and thats it.

 

In control panel under statistics you can fully deactivate the statistics collection for performance improvements.

 

If you have a project that requires a lot of sessions and need to discuss hosting, feel free to contact me or Hostnordic.

Thank you for your replies.  They have been quite helpfull ill be sure to contact u on mail nicolai with future questions if i have them.

I just got a sample from our test guy now , he says the mdb varies.

But it seems like its just trying to open an sqlconnection and not an access database and it just looks like its opening an access database due to the call u make with the API ?, so i dont believe the problem lies on the access databases? I

Please wait!
The SQL-Server database could not be opened ('Dynamic.mdb') - the error is:
 

 System.InvalidOperationException: Timeout expired.  The timeout period elapsed prior to obtaining a connection from the pool.  This may have occurred because all pooled connections were in use and max pool size was reached.
   at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
   at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
   at System.Data.SqlClient.SqlConnection.Open()
   at Dynamicweb.Database.GetConn(String strDatabase)

Just ignore the "Dynamic.mdb" in the error message. The thing is that we use the same method for accessing access and SQL databases (GetConn(String strDatabase), an thus the same error messages. We have multiple access databases, so when we want to fetch data, we pass the filename as a parameter to that method so it knows where to look for the data we're trying to access. When we run in to an exception, we display a message telling what went wrong containing the argumented filename. If you take a closer look at the stack, you'll see that the next step from the GetConn method is  System.Data.SqlClient.SqlConnection.Open, ergo where we connect to the SQL server. So you're absolutely right in your disbeleive that something should be wrong with the Acess database:)