Re: Openrowset Jet OLEDB
From: Ulf Brügelmann (u.bruegelmann_at_omnicom.de)
Date: 04/30/03
- Next message: BP Margolin: "Re: sql connection security"
- Previous message: Brian Lawton: "Re: Which users are connected?"
- In reply to: Mary Chipman: "Re: Openrowset Jet OLEDB"
- Next in thread: Mary Chipman: "Re: Openrowset Jet OLEDB"
- Reply: Mary Chipman: "Re: Openrowset Jet OLEDB"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Wed, 30 Apr 2003 22:40:22 +0200
Ok, sorry if the question was unclear.
Front end app means the app we wrote and wich the users use to modify the
data in the sql server.
The app in question is sort of a provisioning system.
The point is, that users need to import provision data from different
external sources, thus neither database name nor table name are constant.
The way it's working up to now is that the user specifies a mdb via a
fileOpenDialog, the database is opened localy (via DAO) and the choosen
table is then imported sequentialy on a record by record basis.
As the amount of data is growing (now exceeding 100000 records per import)
this is no longer acceptable.
Therefor we tried to speed up the process by importing the data via
OpenDataSource (reducing the time needed from several hours to 2 minutes).
This works fine in our development enviroment where the sql service is
running on the machines system account, but fails in the production
enviroment where the server is running on a domain user account.
Ulf
"Mary Chipman" <mchip@nomail.please> schrieb im Newsbeitrag
news:i290bvkh0n8me1kvsvi755lc2jlqeiole5@4ax.com...
> I'm confused -- are you trying to import all of the tables into SQL
> Server as a one-time operation, or just access the data in the Jet
> database? And what do you mean by "speedily import an mdb into the
> server via the front-end app"? What front-end app?
>
> -- Mary
> Microsoft Access Developer's Guide to SQL Server
> http://www.amazon.com/exec/obidos/ASIN/0672319446
>
> On Wed, 30 Apr 2003 08:03:22 -0700, "Ulf" <u.bruegelmann@omnicom.de>
> wrote:
>
> >Hi there,
> >
> >we're having trouble using OpenDataSource with Jet OLEDB
> >to access a mdb.
> >
> >The layout is as follows:
> >We're running SQL Server 2000 SP3 on a Windows 2000 SP3
> >machine.
> >The SQL Server service runs on a domain admin account (not
> >a good idea, I know). Users are loging in via Windows
> >Authentication.
> >
> >The task was to import a mdb into Sql Server. We tried
> >with OpenDataSource but failed with an errormessage
> >complaining about access rights to the mdb.
> >
> >After some inquiring we found that sp_addlinkserver works
> >but in the setup described above it only does if the mdb
> >is on the same machine as the Sql Server and of course the
> >user must have system administration rights in the sql
> >server to be allowed sp_addlinkserver....
> >
> >As both conditions give us major headaches:
> >Wich user context is actually used when issuing an
> >opendatasource from within the frontend app?
> >
> >Is there any other way to speedily import an mdb into the
> >server via the frontend app?
> >
> >Thanks in advance
> >
> >Ulf
>
- Next message: BP Margolin: "Re: sql connection security"
- Previous message: Brian Lawton: "Re: Which users are connected?"
- In reply to: Mary Chipman: "Re: Openrowset Jet OLEDB"
- Next in thread: Mary Chipman: "Re: Openrowset Jet OLEDB"
- Reply: Mary Chipman: "Re: Openrowset Jet OLEDB"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
