Access versus SQL in FMDesktop

[Anonymous]

I'm trying to decide which version of FMDesktop to recommend, the Access
version or the SQL version. Would anyone care to comment on these
questions?

1. The rule of thumb I've seen is that Access is suitable for up to five
concurrent users--more than that should go to SQL Server. In the FMDesktop
context, does this mean five Facility Manager sessions open simultaneously,
or would Facility Web or Facility Request users also count?

2. Does a procedure to upgrade an FMDesktop database from Access to SQL
exist? I assume it's possible, but would it be a nightmare or a piece of
cake?

3. My organization is already using MS SQL Server for other applications.
Should that affect the decision on which database FMDesktop should use?

Thanks, everyone.

[mark.evans]

Your question 1: When counting concurrent users, you should count each Facility Manager session, one for Facility Request (the server makes one connection, not one for each user), and none for Facility Web viewers (it doesn't attach to the live database). Facility Web publishing does connect to the database, but it is usually replacing a Manager session or running at night. But, if you have a very large number of drawings, Facility Web Publishing can run for a significant period of time and you might want to count it as another concurrent user. In my experience, it is more likely to see performance issues because of WAN speed or because the box hosting the Access database is underpowered. Access itself is not often a limiting factor.

Question 2: There are no automated tools for migrating an FMD Access database to a FMD SQL Server database. We've done it to build test data, and i would say it is closer to nightmare than to piece of cake. It's not logically hard, but getting all the details right and finding the mistakes can be very tedious.

My general guidance to potential customers is to use Access unless there is an overriding reason to go to SQL Server or Oracle. The application still uses Access in the middle even if you run SQL Server or Oracle as your backend database. And these are much trickier configurations to install and maintain. I would only use SQL Server or Oracle if you have people around to support those installations. It sounds like you do if it is a standard in your organization. The other consideration is integration. If you need to do integrations between backend databases (e.g. feeding HR data to FMD), then it is probably easier for your integration team to do it between similar database technologies.

My two cents.

Mark Evans
Autodesk

[Anonymous]

Thanks, Mark. That's the information I was looking for. (for which I was
looking?...)

[Anonymous]

John,

Recommend neither unless you respect your integrity.

Neither Database is acceptable.

Xml is the way to go. We have just written a major app for
a Health organisation that can read a very large XML
app into Acad in 0.1 sec and keep track of it.

Believe me we have struggled in this area for the last 20 years
and it is going nowhere without xml.

You asked! I gave my opinion! You may not like it but there you go!

Regards Gary.




"John Aynesworth" wrote in message
news:5731204@discussion.autodesk.com...
I'm trying to decide which version of FMDesktop to recommend, the Access
version or the SQL version. Would anyone care to comment on these
questions?

1. The rule of thumb I've seen is that Access is suitable for up to five
concurrent users--more than that should go to SQL Server. In the FMDesktop
context, does this mean five Facility Manager sessions open simultaneously,
or would Facility Web or Facility Request users also count?

2. Does a procedure to upgrade an FMDesktop database from Access to SQL
exist? I assume it's possible, but would it be a nightmare or a piece of
cake?

3. My organization is already using MS SQL Server for other applications.
Should that affect the decision on which database FMDesktop should use?

Thanks, everyone. Message was edited by: Discussion Admin

[Anonymous]

SQL Server 2005 supports XML as a native file type. SQL Server 2008 soon to
be released even greater support for XML. Using XML is appropriate in
certain contexts --but-- SQL Server remains the wiser solution as it
provides so much more functionality than a specific file type offers and XML
is really nothing more than a specific file type hence, all data processing
when using XML (for the most part in the context of CAFM) all solutions must
be coded manually.

Just two features such as SQL Server Reporting Services and SQL Server
Notification Services squashes the argument of using XML files and only XML
files.

As for Access/JET? It is an outdated monolithic application/database and the
JET database which the Access GUI is based on has been discontinued or at
the very least frozen at JET 4.0 as I understand. It does not scale up but
does have benefits as the .mdb database file is more portable and can be
copied and backed up easier.

Finally, XML is hierarchical while SQL Server is relational. All data
management is no longer one or the other but hybrid which again makes SQL
Server the wisest choice IMO and in my experience as a web developer.

<%= Clinton Gallagher
NET csgallagher AT metromilwaukee.com
URL http://clintongallagher.metromilwaukee.com/






"Gary D'Arcy" wrote in message
news:5763077@discussion.autodesk.com...
John,

Recommend neither unless you respect your integrity.

Neither Database is acceptable.

Xml is the way to go. We have just written a major app for
a Health organisation that can read a very large XML
app into Acad in 0.1 sec and keep track of it.

Believe me we have struggled in this area for the last 20 years
and it is going nowhere without xml.

You asked! I gave my opinion! You may not like it but there you go!

Regards Gary.




"John Aynesworth" wrote in message
news:5731204@discussion.autodesk.com...
I'm trying to decide which version of FMDesktop to recommend, the Access
version or the SQL version. Would anyone care to comment on these
questions?

1. The rule of thumb I've seen is that Access is suitable for up to five
concurrent users--more than that should go to SQL Server. In the FMDesktop
context, does this mean five Facility Manager sessions open simultaneously,
or would Facility Web or Facility Request users also count?

2. Does a procedure to upgrade an FMDesktop database from Access to SQL
exist? I assume it's possible, but would it be a nightmare or a piece of
cake?

3. My organization is already using MS SQL Server for other applications.
Should that affect the decision on which database FMDesktop should use?

Thanks, everyone.

Message was edited by: Discussion Admin