Web Wiz - Green Windows Web Hosting

  New Posts New Posts RSS Feed - Access to SQL Server - Step by Step
  FAQ FAQ  Forum Search   Events   Register Register  Login Login

Access to SQL Server - Step by Step

 Post Reply Post Reply Page  123 12>
Author
netmasterjohn View Drop Down
Newbie
Newbie


Joined: 13 December 2004
Status: Offline
Points: 3
Post Options Post Options   Thanks (0) Thanks(0)   Quote netmasterjohn Quote  Post ReplyReply Direct Link To This Post Topic: Access to SQL Server - Step by Step
    Posted: 13 December 2004 at 8:25pm
There seems to have been a lot of request for a step by step guide on how to migrate the Access version to SQL Server, so here is my attempt at giving you one.

1. Open Enterprise Manager for the SQL Server

2. Create a blank (empty) database on the SQL Server

3. Go to Tools, Data Transformation Services, Import Data

4. Use the Import wizard to get the info from the Access .mdb file:

    - Choose a datasource: Use DropDown menu and scroll up until you see Microsoft Access
    - Select Microsoft Access from the dropdown list, this will change the options on the tab
    - In the FileName section, browse to where you have the WebWiz database stored and select the file
    - Add a username and or password if necessary (by default it isn't)

    Click Next and this brings you to the Destination tab
    - Leave the default Destination value of "Microsoft OLEDB Provider for SQL Server"
    - Fill in your server information on this tab
    - Don't forget to select your new empty database from the dropdown list at the bottom
   
    Click Next and this brings you to the "Specify Table Copy or Query" tab
    - Select the first option "Copy Tables and Views from the Source Database"
   
    Click Next to see a list of all the tables that you can copy to the new database
    - Select All

    Click Next and let it go.

After all the data is imported (this should be error free, if it wasn't, maybe you already had some data
in your destination database, delete it all and try again)

Then modify the SQL_server_connection.asp file in the Forum/Admin folder

Lines 59, 60, 61 and 62 are the important ones... Just fill in the name of your SQL Server, User
name, password and the name of the empty database that you just populated.

Save your changes and then run the msSQL_server_setup.asp file in the main Forum folder.

This will create all the necessary stored procedures to run the SQL Server version of WebWiz.

It will generate some errors, this is simply because it is trying to create the tables that you've already
imported from the access file. Don't worry about them. The important thing to get out of running this script
are all the stored procedures.

Once the msSQL_server_setup.asp script is finished, you are done.

Check your tables in the SQL Server via Enterprise Manager if you want to make sure the data is there, but
you should be able to log into the forum and use it right away.

This process worked perfectly for me and hopefully it will help you as well but I do not guarantee anything. :-)



Edited by -boRg- - 05 January 2006 at 3:09pm
Back to Top
ukakht View Drop Down
Newbie
Newbie


Joined: 09 December 2004
Location: Scotland
Status: Offline
Points: 14
Post Options Post Options   Thanks (0) Thanks(0)   Quote ukakht Quote  Post ReplyReply Direct Link To This Post Posted: 14 December 2004 at 6:20am
I've tried all,  but no luck,
 
I can't post nor can send pm
 
Back to Top
ukakht View Drop Down
Newbie
Newbie


Joined: 09 December 2004
Location: Scotland
Status: Offline
Points: 14
Post Options Post Options   Thanks (0) Thanks(0)   Quote ukakht Quote  Post ReplyReply Direct Link To This Post Posted: 14 December 2004 at 6:27am
I get this error when sending pm or posting posts

ADODB.Recordset error '800a0cb3'

Current Recordset does not support updating. This may be a limitation of the provider, or of the selected locktype.

/webwiz/pm_post_message.asp, line 306

Please help me
 
Back to Top
netmasterjohn View Drop Down
Newbie
Newbie


Joined: 13 December 2004
Status: Offline
Points: 3
Post Options Post Options   Thanks (0) Thanks(0)   Quote netmasterjohn Quote  Post ReplyReply Direct Link To This Post Posted: 14 December 2004 at 10:15am
Sorry about that, it seems my initial post was premature.

Here is an updated answer on how to do the conversion from Access to SQL Server.

Step 1. Create the empty database on SQL Server
Step 2. Modify the SQL_server_connection.asp file in the Forum/Admin folder (Lines 59, 60, 61 and 62) to enter your SQL Server info.
Step 3. Run the msSQL_server_setup.asp file in the main Forum folder.
(By running this script now, it avoids the problem that was created before that would not let you post)
Step 4. Do the Tools, Data Transformation Services, Import Data thing in Enterprise manager as described above except for 2 changes.
 - Do the import in 2 stages. First import All tables from the access database EXCEPT the Group, Thread and BuddyList tables.
After all the rest are imported, then go back and import the Thread and BuddyList tables. Leave the Group table alone because it is already in the SQL Server version (created by the Setup script)

- When you are importing the tables in the Enterprise Manager wizard, in the "Select Source Tables and Views" window, click on the ... under the Transform column for each table that you are importing and in the "Column Mappings and Transformations" window that opens, click "Delete Rows in Destination Table" and make sure the "Enable Identity Insert" option is checked.
Do this for each table that you import and you should be fine. I have done these steps and have full functionality.
Back to Top
Corey Bryant View Drop Down
Newbie
Newbie


Joined: 14 December 2004
Status: Offline
Points: 18
Post Options Post Options   Thanks (0) Thanks(0)   Quote Corey Bryant Quote  Post ReplyReply Direct Link To This Post Posted: 14 December 2004 at 10:25am
Originally posted by ukakht ukakht wrote:

I get this error when sending pm or posting posts

ADODB.Recordset error '800a0cb3'

Current Recordset does not support updating. This may be a limitation of the provider, or of the selected locktype.

/webwiz/pm_post_message.asp, line 306

Please help me
 
I get the same thing.  I was told it had to to with the locktype: To be updateable, the locktype must be at least optimistic.  But I am at a loss on that part.  No problems converting or anything.
Back to Top
netmasterjohn View Drop Down
Newbie
Newbie


Joined: 13 December 2004
Status: Offline
Points: 3
Post Options Post Options   Thanks (0) Thanks(0)   Quote netmasterjohn Quote  Post ReplyReply Direct Link To This Post Posted: 14 December 2004 at 11:27am
Follow my second post, ignore the first step by step. The stuff that causes the "ADODB.Recordset error '800a0cb3'" is eliminated by following the steps in my second post. It is simply a matter of how the tables and stored procedures are created, doing things the way I did it the first time tries to do too many things at once and the Recordset can't handle it.

Doing things the second way works great.

Check out my site for proof.

http://www.epcmedic.com
Back to Top
persepherone View Drop Down
Newbie
Newbie
Avatar

Joined: 15 December 2004
Status: Offline
Points: 4
Post Options Post Options   Thanks (0) Thanks(0)   Quote persepherone Quote  Post ReplyReply Direct Link To This Post Posted: 15 December 2004 at 6:21am
how many members is good enough for moving on to SQL server.......
wat i want to know is that though it is well known that access supports small database sizes with fewer DB calls but exactly how much members & how many daily/simultaneoul hits R  gud enough to move onto SQL ????
Back to Top
dj air View Drop Down
Senior Member
Senior Member
Avatar

Joined: 05 April 2002
Location: United Kingdom
Status: Offline
Points: 3627
Post Options Post Options   Thanks (0) Thanks(0)   Quote dj air Quote  Post ReplyReply Direct Link To This Post Posted: 15 December 2004 at 8:49am
i use SQL for all my databases. what ever they are for.

but if you know your site is going to get bigger then i advise to use SQL if available to you, or you find its getting a bit slugish.

there are exact figures as it can depend on the load and state of the server.

for a couple of friends its more wearth while staying with access.

the main thing that good with SQL is that it can search faster and better performance.


Back to Top
 Post Reply Post Reply Page  123 12>

Forum Jump Forum Permissions View Drop Down

Forum Software by Web Wiz Forums® version 12.08
Copyright ©2001-2026 Web Wiz Ltd.


Become a Fan on Facebook Follow us on X Connect with us on LinkedIn Web Wiz Blogs
About Web Wiz | Contact Web Wiz | Terms & Conditions | Cookies | Privacy Notice

Web Wiz is the trading name of Web Wiz Ltd. Company registration No. 05977755. Registered in England and Wales.
Registered office: Web Wiz Ltd, Unit 18, The Glenmore Centre, Fancy Road, Poole, Dorset, BH12 4FB, UK.

Prices exclude VAT at 20% unless otherwise stated. VAT No. GB988999105 - $, € prices shown as a guideline only.

Copyright ©2001-2026 Web Wiz Ltd. All rights reserved.