I've done a number of other tests and SQL Server wins each time as you'd expect - usually in less than half the time. How I did these tests was to arrange 2 browser side-by-side vertically on the screen and then click an operation on the forum with the Access DB and then immediately go over to the browser and click the same operation (e.g. Members link) on the SQL DB forum. This gave the Access forum an advantage because the operation was kicked off there a split second earlier but the SQL forum (as one would expect) always outperformed.
Now going on what ruirib says, if I managed to index and set-up the SQL Server DB properly and get the indexes etc. right then I'm assuming that the SQL forum will do even better.
You can then use SQL Server Management Studio to generate the a script to create the database. Once it is created, you can execute in your host's server. Then, use DTS to export the data from the local SQL Server DB to the hosts DB.
Why can you not generate a backup DB from the local one and then restore/import it into the hosted one?
The only problem that I can find at the moment is the fact that a new topics "Read" count does not increment - this is puzzling because it's such a simple SQL update call.
That's a problem with the default values for the column. You won't be able to restore a DB without Enterprise Manager / Management Studio.
A problem that occurred sometimes while upsizing an Access DB was the creation of a trigger that caused problems when deleting or moving posts (not sure). Better be sure that doesn't happen.
You won't be able to restore a DB without Enterprise Manager / Management Studio.
1&1 have an option in the SQL Server Management section of their web: "Import your Microsoft Access Database or an SQL backup file to the MS SQL Server."
Do you not think that the "import" function executes the same API that the Enterprise Manager would?
(BTW - thanks for all your comments here - really helping me and much appreciated.)
A problem that occurred sometimes while upsizing an Access DB was the creation of a trigger that caused problems when deleting or moving posts (not sure). Better be sure that doesn't happen.
I've tested lock, move and delete and all seem okay right now.
That's a problem with the default values for the column.
I figured that I could do 1 of 2 things to solve this: Change the default value for the table OR change the code to populate 0 on initial insert.
Because 1&1 SQL Admin was playing up and I couldn't get to the SQL executer I changed the code in post_info.asp so that 0 is inserted into T_VIEW_COUNT during the topic creation process and this seems to have solved that problem.
Topic Locked
Posted - 28 July 2006 : 14:09:53
