Buy Support
Incidents |
If you can't find your answer
in the FREE PUBLIC QDeveloper Forum, require URGENT Priority Support, or you need to send us
private or confidential information: |
Click Here
|
If you can't
login and post questions or you are having trouble viewing forum posts:
Click Here
|
Callback
Support |
If you live in USA, UK, Canada, Australia or New
Zealand, you can leave us details on your question and request us to call you back and discuss
them with you personally (charges apply). |
Click Here
|
Buy Support
Incidents |
If you can't find your answer
in the FREE PUBLIC QDeveloper Forum, require URGENT Priority Support, or you need to send us
private or confidential information: |
Click Here
|
|
SQL Server SSIS Nightly Import 24 QB Databases |
Author |
Message |
|
Posted : 2007-05-03 03:30:51 |
I have 24 different company QB files that are all subsidiaries of our main company. I need to import all of them into SQL Server every night. Is this possible?
My concern is that I read the instructions on how to use DTS, but it appears that you have to leave the company file open during the process. If that is the case, how do I have all 24 different company files open?
I have QB Enterprise 6.0 and SQL Server 2005 and will be using SSIS (the new form of DTS).
Thanks,
Dave |
|
|
|
Tom |
|
Group | : Administrator |
Posts | : 5510 |
Joined | : 2006-02-17 |
|
Profile |
|
Posted : 2007-05-03 10:31:47 |
Yes it's possible, but instead of using DTS you need to use a stand-alone desktop application that can run through all 24 DSNs (for the 24 company files) one at a time. The other approach would be to script the linking and unlinking of 24 different QODBC linked servers under SQL Server 2005 as I assume you have 24 SQL databases, one for each subsidiary. |
|
|
|
|
Posted : 2007-05-04 01:37:11 |
Actually I will only have one SQL database. When I import the data I will put it into custom tables that will flag each record as to which QB company it belongs to. For example, I will make an "accounts" table that is identical to the "accounts" table in QB but I will add one extra field called "company" and then populate that field with the name of the company file being imported.
My biggest concern was regarding whether or not I have to have QB open, with the company file open, when I run my script? I will create 24 separate DSNs, one for each company file, and then run through them one at a time like you suggest. But will it work if the company file isn't already open in QBs?
Also, which version of QODBC would work the best? I read about using the server version, but I also read about using a web version. My server will run SQL Server (and IIS if needed), will have QB installed on it, and will have all 24 company files on it. Thanks for the help! |
|
|
|
Tom |
|
Group | : Administrator |
Posts | : 5510 |
Joined | : 2006-02-17 |
|
Profile |
|
Posted : 2007-05-04 08:51:09 |
Your company files would all be configured to work in unattended mode which means that when each DSN connects it will launch QuickBooks and open the appropriate company file. You would then close the connection, wait, and then open the next connection etc. Basically QuickBooks gets called by QODBC, but if a company file is already open the connection will fail.
I don't believe this will work using DTS, SSIS or SQL Server as Windows Services require quite a bit of time to be released when connections are closed, but you're welcomed to try (that's why we have 30 day evaluations). Using a desktop program will just need the QODBC Desktop Edition.
See: How do I setup QODBC to auto-login into QuickBooks and start it if it's not running? for more. |
|
|
|
|