Question on QB Enterprise Version User Controls

Posted by W on December 19, 2008, 5:48 pm

Please log in for more thread options

I read somewhere that the Enterprise version of QB now uses SQL. Is it
using SQL for all transactions? I am hoping to find a version that does
not give individual users read write access to the Quickbooks data file
through the Windows file system, and use of an SQL database process that
runs separately from the user's Quickbooks process should allow for that .

How robust are the user controls in the Enterprise version?

--
W

Posted by Haskel LaPort on December 19, 2008, 10:12 pm

Please log in for more thread options

>I read somewhere that the Enterprise version of QB now uses SQL. Is it

> using SQL for all transactions? I am hoping to find a version that does

> not give individual users read write access to the Quickbooks data file

> through the Windows file system, and use of an SQL database process that

> runs separately from the user's Quickbooks process should allow for that .

> How robust are the user controls in the Enterprise version?

QuickBooks uses MySQL not Microsoft SQL.

> --

> W

Posted by W on December 20, 2008, 1:47 pm

Please log in for more thread options

> >I read somewhere that the Enterprise version of QB now uses SQL. Is it

> > using SQL for all transactions? I am hoping to find a version that

does

> > not give individual users read write access to the Quickbooks data file

> > through the Windows file system, and use of an SQL database process that

> > runs separately from the user's Quickbooks process should allow for that

> >

> > How robust are the user controls in the Enterprise version?

> QuickBooks uses MySQL not Microsoft SQL.

So what is the implication of that? Are users sharing access to a flat
file or going through a server?

--
W

Posted by klunk on December 20, 2008, 9:37 pm

Please log in for more thread options

>> I read somewhere that the Enterprise version of QB now uses SQL...

> QuickBooks uses MySQL not Microsoft SQL.

MySQL is an open source database product.
http://www.mysql.com

Unless there has been a recent change of which I am not aware,
QuickBooks uses a locked version of the Sybase
SQLAnywhere database server -- since the 2006 version.
http://www.sybase.com
The Intuit QB version is locked in the sense that there is no
way to query it directly using SQL statements. All external
access to the data has to go through the QB SDK.

As for Enterprise, I believe it's the same engine, just with less
restrictions on list size and possible some performance
enhancements

Posted by W on December 20, 2008, 11:46 pm

Please log in for more thread options

> >> I read somewhere that the Enterprise version of QB now uses SQL...

> >

> > QuickBooks uses MySQL not Microsoft SQL.

> >

> MySQL is an open source database product.

> http://www.mysql.com

> Unless there has been a recent change of which I am not aware,

> QuickBooks uses a locked version of the Sybase

> SQLAnywhere database server -- since the 2006 version.

> http://www.sybase.com

> The Intuit QB version is locked in the sense that there is no

> way to query it directly using SQL statements. All external

> access to the data has to go through the QB SDK.

> As for Enterprise, I believe it's the same engine, just with less

> restrictions on list size and possible some performance

> enhancements

The question is whether the SQL server is running in a separate process
space, or do individual users end up sharing a flat file that they all
access read/write on the file system?

Running SQL in a separate process makes it possible to achieve a very good
level of security. Running users with shared read/write access to a file
on the file system makes security almost meaningless. A user could just
copy the entire file and do with it what they like.

--
W