Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
El Kabong
Starting Member
3 Posts |
 Posted - 2002-08-18 : 12:41:35
|
| My company is running SQL Server 2000 on a Windows 2000 server, and have a number of databases used for storing client data.When they first implemented SS2K, both the data and transaction logs for the databases were stored on the same drive. Some months later, other drives were added to the server, and the decision was made to store the transaction logs on one of the new drives.We've had no problems executing jobs or packages against the DB's whose logs are on the new drive, but when we try to run an Export Data procedure on those databases, we get an error that says we're not authorized to access the transaction log drive. All of our ID's have been given full authority to all drives, and we're stumped as to what could be causing the problem. |
|
|
sandesh_moghe
Constraint Violating Yak Guru
310 Posts |
Posted - 2002-08-19 : 01:16:58
|
| Which type of job you have created?Is it created before transfering the log file?---------------------------Sandesh - The Messanger |
 |
|
|
El Kabong
Starting Member
3 Posts |
Posted - 2002-08-19 : 01:29:51
|
| It's not a job. It's the "Export Data" function available by right-clicking on the database icon. |
|
|
|
|
|
|
Security error