It's a design problem. The table is TRUNCATED/LOADED/REFRESHED
You can
A. Extract the structure
1. Create a distinct database with the large table, its indexes and the Access user as dbo.
2. Change the original table to view
3. Roles / DB users needed in each database (without rights chaining used)
Or
B. Extract the process
1. Modify Access application to create an CSV file instead of the large pass-thru query, export is finished by creating an indicator file.
2. Create a network share on Windows Server hosting SQL Server
3. Create a SQL Agent job checking the share for indicator and moving files to internal folder
4. Create job steps started by previous step as dbo user reloading the table
5. Indicate result in table/file/message back to the initialing user
Main Topics
Browse All Topics





by: jimpenPosted on 2007-08-13 at 10:45:12ID: 19686104
You would create an application role on the server and add that user to the role. That should give the id the permissions it needs.