[AccessD] Upsizing to SQL Server

Dan Waters dwaters at usinternet.com
Wed Dec 21 15:51:23 CST 2005


Some Progress!

SS 2005 has a Configuration Manager.  In this you need to set the Network
Configuration.  By default, only shared memory is Enabled.  To get an Access
Project to work with SS 2005 you also need to set TCP/IP as Enabled.

Apparently any FE that isn't based on .Net 2.0 framework is considered a
down-level client, and can only connect to SS 2005 through network access.

So, this time when I tried to upsize, AXP did find the SQL Server Express
database, the data was moved to SSX, and the FE was converted to an ADP.
But I was reminded again that I am not a guru because there was a 23 page
report of errors!  I'll fix them and try again.

Dan

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Dan Waters
Sent: Wednesday, December 21, 2005 2:59 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Upsizing to SQL Server

Hello John!

I'm looking at this too.

I pre-ordered a book titled Beginning SQL Server 2005 Express, and got it 2
days ago.  Author is Rick Dobson.

He does specifically say that you can create an Access Project that points
to SSX, although he doesn't talk about upsizing per se.  I tried to select
my installed SSX database from the upsizing wizard in AXP, and wasn't able
to do so.  I may not have the 'service broker'(?) set up correctly.

He also specifically talks about creating links from an mdb that point to
SSX.  You do need ODBC to do this.  He doesn't talk about faster, slower,
etc.  

According to SQL 2K5 Books On Line, you can import data a few different
ways.  Look at Importing Data.

That's all I know for now.

Dan Waters


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of John Colby
Sent: Wednesday, December 21, 2005 1:05 PM
To: 'Access Developers discussion and problem solving'
Subject: [AccessD] Upsizing to SQL Server

I have a rather large application that I would like to upsize to SQL Server
express.  My concern is that this is a "mission critical" app and am
wondering how to do this.  First, can the express edition be selected from
the Access upsizing wizard?  Second, there are 40 users.  I have no idea
what the actual impact will be on the speed of the app etc.  This would be a
straight data update at first, i.e. just moving the data to the Express
server and linking via odbc (I assume) so that the app works "just like an
access BE".  Since I can't predict the impact, I can't really say whether it
will stand up to the load, be faster, slower, immensely slower etc. and thus
can't just recommend that we "just do it".  SQL Server has a bunch of
improvements that recommend it in general but I have no feel for whether
this would really work.

Has anyone ever done something like this?  The Access BE is approaching 500
mbytes now, with about 40 concurrent users.

John W. Colby
www.ColbyConsulting.com 

Contribute your unused CPU cycles to a good cause:
http://folding.stanford.edu/

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com




More information about the AccessD mailing list