Welcome to MSDN Blogs Sign in | Join | Help
Set up Office Accounting for multiple users

I just saw this article on how to set up Office Accounting for multiple users. As I know this is a topic that people has a lot of questions about I thought I would post a link to it...

At the same time you can find a lot of usefull information in the How To section on that site.

Enjoy

 

 

Posted: Tuesday, May 13, 2008 8:14 PM by Jorn
Filed under:

Comments

atul_m_joshi said:

Hi,

My queries might be out of this thread, but thought will post anyway as any help is much appreciated...

We have an intranet asp .net application which is used by around 20 users. This application adds/fetches data to/from SBA 2006 mostly through AIP's and on some occasions through direct sql calls to MSDE database. Now we are facing multi user problems here i.e. getting server busy kind of errors, high CPU consumption and prolonged responses from the app... Now questions are as follows...

1.Direct SQL access to the MSDE database for SBA 2006 is supported way for an application ?

2.Do SBA 2006 API’s (SBAAPI.dll) is designed to be used in multiuser environment like ASP .NET app ?

3.We get errors like “Database Busy” while accessing asp .net pages which internally uses SBAAPI.dll, how do we manage timeouts or command waiting  time settings ?

4.Is running SQL 2005 is supported database for SBA 2006 ?

5.While using SBA API’s in multi user environment, is making only single connection across users is recommended or do each user need to use different connection using Logon method ?

6.In multi user environment i.e. while SBA API calls being made from different users often CPU usage reaches more than 50% for msde sql server process. Do we have any way to optimise this processing

Any help is quite welcome...

Best regards,

Atul

# May 22, 2008 1:56 AM

Jorn said:

Wow, a lot of questions, I’ll try to answer to the best of my knowledge.

1: Direct access? well depends… we do not recommend writes as that can bypass some of the business logic, for reads it should be ok.

2. Again depends :o) the API is not thread safe if that is what you are asking. But you can make it work by arranging your code to serialize your calls to the API or by using multiple instances.

3. see 2. But this question can have many aspects to it. Your problem could be a performance problem because of the data you are using or the way you are using them. I do have other blog posts that talk a little about performance and things to think about when you use the API. In general you can not change the timeouts that we use internally in the API but you can do things like retrying in your code.  

4: You can not use SQL server 2005 with Small Business Accounting 2006, to use SQL Server 2005 you will need to upgrade to a newer version of Office Accounting (2007 or 2008)

5: see 2.

6: Maybe … take a look at some of my other blog posts about performance and coding for performance, they may help.

I know my answers here are kind of vague, but without knowing the details of your problems this is kind of hard…

# May 23, 2008 12:22 PM

atul_m_joshi said:

Good to get some directions from you...

Yup actually I did implement code for retry on specific server busy errors few days back, solved that problem on my development machine, hoping to get positive response from UAT.

There is also plan to upgrade application to MOA 2007, but as proof of concept we might run few tests of 2006 with full sql 2005.

Hopefully we are moving in right direction, but still CPU usage while calling functions which are using lots of API calls is worrying me; its always above 50% on dual core 4GB RAM server, but I believe that might be solved after moving to full SQL server which might be able to use both CPU's and more RAM which is not the case with MSDE database.

Will post our outputs, if any, here,

Again thanks for your response, much appreciated...

# May 24, 2008 1:22 PM

Jorn said:

Why not go to 2008 when you upgrade?

# May 27, 2008 11:27 AM
Anonymous comments are disabled
Page view tracker