DataBase - MS SQL Express 2008

Asked By Peter
21-Apr-10 01:21 PM
Hi all,
in order to increase performance of my Access 2007 application i choose to
split the backend to a SQl Express 2008 Database engine. However..this seems
not to function..i receive an error message saying - The Upsizing Wizard does
not work with the version of Microsoft SQL server to which your project is
connected..I cannot find anything related to this issue on the Microsoft
Update Website..

Any suggestions?

Thanks!
SQL Express 2008
(1)
SQL Server
(1)
Access 2007
(1)
Servername
(1)
Database
(1)
Soooooooooooo
(1)
Recordset
(1)
Editionof
(1)
  Paul Shapiro replied to Peter
22-Apr-10 09:00 AM
I am not sure, but I doubt Access 2007 can control SQL 2008. Access has never
worked with SQL versions that came out later than the Access version. You
could:

1. Use SQL Express 2005 and then update the db to SQL Express 2008 after the
conversion.
2. Use SQL Server tools to import the Access db, except I am not sure if the
tools are included in the SQL Express edition. You can buy the SQL 2008
developer edition for about $50 which includes all tools, or maybe a trial
version would work if it is a one-time conversion.
3. You could manually create the db structure in SQL Server and then import
the data.

But if the only reason you are moving the backend is to improve performance,
you may be disappointed. Access is very fast running on a stable LAN with a
reasonable number of users. SQL Server offers less corruption, better
security, more robust recovery, effective WAN access, and enhanced data
engine features. But performance of equally well-designed structures may not
change unless you have particular performance issues now.

If your current Access db is not yet split, you might want to first split it
into an Access backend and see how performance goes. Assuming you have been
running an unsplit db from your local drive, and you split the backend onto
a network drive, you may lose a little performance, but it should not be
much for most applications.
  Stefan Hoffmann replied to Peter
22-Apr-10 09:13 AM
hi Peter,

hmm, I have not tried the Access 2007 Upsizing Wizard, but the 2003
version works.

You can use instead of the wizard the SSMA tool:


http://www.microsoft.com/downloads/details.aspx?FamilyID=133b59c2-c89c-4641-bebb-6d04476ec1ba&DisplayLang=en


mfG
--> stefan <--
  a a r o n . k e m p f replied to Peter
22-Apr-10 10:34 AM
Access 2007 works best with SQL 2005, and there is an express edition
of that (with free SSMS Express)





o
ems
does
s
  Peter replied to Paul Shapiro
22-Apr-10 05:32 PM
Thank you all for some very usefull suggestions. The current Access 2007 is
split and we are 10 users. The performance issue is most related to WAN
connection...i iwll see what i can do with all your kind information..once
again..Thanks You!
  Tony Toews [MVP] replied to a a r o n . k e m p f
23-Apr-10 12:29 AM
But, once you are past the upsizing issue it will work very well with any other
version of SQL Server.

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/
Granite Fleet Manager http://www.granitefleet.com/
  Tony Toews [MVP] replied to Stefan Hoffmann
23-Apr-10 12:30 AM
it is my understsnding this tool does a better job than tthe built-in wizard.

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/
Granite Fleet Manager http://www.granitefleet.com/
  Paul Shapiro replied to Peter
23-Apr-10 07:17 AM
If your purpose is supporting WAN users, you should definitely consider
changing form record sources from something like:
Select * From MyTable
to retrieving a single row at a time as requested by the user. Unless the
row count is pretty small, retrieving all rows becomes a serious time delay
on a WAN.

I use a record source like this so the form opens with the appropriate
metadata but no actual data:
Select * From MyTable Where 1=0

Most forms have some kind of control(s) for a user to select a row to be
viewed. Instead of finding a row in the form's existing recordset based on
those conditions, you change the form's record source to specify those
conditions.
  a a r o n . k e m p f replied to Paul Shapiro
24-Apr-10 11:09 AM
wow only a retard would run jet over a WAN.

ADP runs soooooooooooo much better, OMG





ay
n
7
nce
You
er
f
8
ith
a
ay
lit
een
be
ose
is
  a a r o n . k e m p f replied to Peter
24-Apr-10 11:11 AM
moving to ADP is what you need to do.. Jet just is not reliable enough
for multiple users

and 3 additional layers of BS is not necessary

File, New, Project (new data)
or
File, Connection, Servername



o
ems
does
s
Create New Account
help
Roger Jennings on Access / Sharepoint DataBase http: / / www.quepublishing.com / articles / article.aspx?p = 1606238 I was very dismayed reading this article, is it makes it pretty clear that in-house hosting of your Sharepoint server with Access Services to support browser-based Access apps is something only large companies will be able to afford, because the pricing and licensing for the Enterprise version is very, very steep. The alternative is hosted Sharepoint / Access Services, and the costs do not seem terribly high. It seems to me that the pricing is upside-down. Big enterprises do not want to deploy Access apps in the browser - - they will build their own .NET apps, browser-based or not 2010 does not really save them money (because of the 64-bit requirements of Sharepoint Server 2010, it could vastly increase those costs for organizations with legacy hardware). The features of
SQL query slow DataBase Hi In the code below I found that it takes 1.3 seconds to load. There is a possible reason, it reads from a local MDB file (access), and it reads from some 270000 rows (result some 15-20 rows, where the highest are counted 150000, 50000, 40000, 26000, remaining are 100's). This is probably more Access that Visual Studio, though - is there a way to split it up or cancel the query? And can I read this faster? string sql = EquipmentID(Equipment) + StartDate.ToOADate().ToString(FloatFormat, myCulture) + EndDate.ToOADate().ToString(FloatFormat, myCulture sql + = " group by event_id, name"; _Log("Calc thread #2"); OleDbCommand com = new OleDbCommand(sql, con); _Log("Calc thread #3"); From #2 to #3 it takes 1.3 seconds. Remaing code takes less that 0.1 second. So the query is what slows it down. Access Discussions SQL Server (1) Linson Unlike Albert D. Kallal (1) MySQL (1) Windows Server 2003
Aaron Kempf's MCITP DBA proof DataBase https: / / mcp.microsoft.com / authenticate / validatemcp.aspx transcript: 944364 AccessCode: helloworld Access Discussions SQL Server 2008 R2 (1) SQL Server 2008 (1) SQL Server 2005 (1) Microsoft SQL Server Reporting Services (1) Regards Larry Linson Microsoft
Using Mysql or SQL server as backend to Access front end DataBase Have a client having problems with a fairly complex Access system which is split into front end and back end. Using access 2003 / mdb format with Access 2007 software. We are surmising that recent server problems or connectivity problems may be to blame
Access to SQLServer GCE DataBase I = 92m trying to step up from being a decent Access Programmer, to including SQLServer in my repertoire and am running into a conceptual design problem component would be = 93awaiting repair = 94 How do I pass this status date from the Access front end to the SQLServer so I can make a view that includes the status on the desired status date? I know I can pull all the data to the Access front end and do the processing there, but that seems wildly inefficient! Note I am thousands of components and hundreds of thousands of events if that makes any difference. Thanks Access Discussions SQL Server (1) Larry Linson Microsoft Office Access (1) SharePoint (1) InfoPath (1) Microsoft SQL Server (1