hi all,
I hace a DTS package that contains a transformation task and an ActiveX Script Task (the last task accesses the registry in order to read some values). So first, does anybody knows under what user account the DTS package will run? and second what permissions should the account have in order to execute the DTS?.
Thanks in advance.
God Bless.The answer is that it depends (you knew I was going to say that).
If it is run interactively, it will run under the login of whoever is logged in (it will also run in the client context of your login, so if you are using EM from a client workstation and are not using it through Terminal Services, watch out!)
If it is run via a SQL Server job, then it will run in the context of the SQL Agent Service.
If you schedule it using NT Scheduled tasks, you can specify the user when setting up the task.
If ou execute it from an SP, I think you can specify the user context (though I don't swear to that -- it might pick up the user context of the person executing the SP).
Originally posted by mvargasp
hi all,
I hace a DTS package that contains a transformation task and an ActiveX Script Task (the last task accesses the registry in order to read some values). So first, does anybody knows under what user account the DTS package will run? and second what permissions should the account have in order to execute the DTS?.
Thanks in advance.
God Bless.
Showing posts with label accesses. Show all posts
Showing posts with label accesses. Show all posts
Tuesday, March 27, 2012
Wednesday, March 21, 2012
DTS connection to Oracle 8; To be upgrated to Oracle 9i. Any guida
I have inherited a Sql Server 2000 instance who's DTS accesses an Oracle 8
database. That Oracle 8 database is going to be upgraded to Oracle 9i soon,
and I was wondering what I have to do to keep this all running. I think I
have to upgrade the Oracle client on the Sql Server box to 9i (since the
Oracle 8 client can not talk to Oracle 9i). Other than that, I am not aware
of anything else I have to do.
Anyone done this before?
Thanks,
Michael
"Snake" wrote:
> I have inherited a Sql Server 2000 instance who's DTS accesses an Oracle 8
> database. That Oracle 8 database is going to be upgraded to Oracle 9i soon,
> and I was wondering what I have to do to keep this all running. I think I
> have to upgrade the Oracle client on the Sql Server box to 9i (since the
> Oracle 8 client can not talk to Oracle 9i). Other than that, I am not aware
> of anything else I have to do.
> Anyone done this before?
> Thanks,
> Michael
|||You should be able to upgrade the Oracle client from 8 to 9i on your side to
solve this problem. My suggestion is to install Oracle 9i on the SQL Server
machine in parallel with the Oracle 8 client. To do this, copy your DTS
package into a new one with a similar name. Create a new DSN that uses the
Oracle 9i client and then test it on the server to make sure the Oracle 9
install worked successfully. Since the Oracle 9i client can read an Oracle 8
database you can switch to this install early and then you'll be prepared
early for the production change on the source database. After the source
database is upgraded to Oracle 9i, you can safely remove the old Oracle 8i
components from your server.
"Snake" wrote:
> I have inherited a Sql Server 2000 instance who's DTS accesses an Oracle 8
> database. That Oracle 8 database is going to be upgraded to Oracle 9i soon,
> and I was wondering what I have to do to keep this all running. I think I
> have to upgrade the Oracle client on the Sql Server box to 9i (since the
> Oracle 8 client can not talk to Oracle 9i). Other than that, I am not aware
> of anything else I have to do.
> Anyone done this before?
> Thanks,
> Michael
|||Also, keep in mind that Oracle's new DATETIME data type has "known" issues
with respect to SQL Server.
Do a search on the net for issues and the workarounds.
Sincerely,
Anthony Thomas
"Amrith" <Amrith@.discussions.microsoft.com> wrote in message
news:5C126AC9-DF98-4B2A-8F8A-E5D887A502AB@.microsoft.com...
You should be able to upgrade the Oracle client from 8 to 9i on your side to
solve this problem. My suggestion is to install Oracle 9i on the SQL Server
machine in parallel with the Oracle 8 client. To do this, copy your DTS
package into a new one with a similar name. Create a new DSN that uses the
Oracle 9i client and then test it on the server to make sure the Oracle 9
install worked successfully. Since the Oracle 9i client can read an Oracle 8
database you can switch to this install early and then you'll be prepared
early for the production change on the source database. After the source
database is upgraded to Oracle 9i, you can safely remove the old Oracle 8i
components from your server.
"Snake" wrote:
> I have inherited a Sql Server 2000 instance who's DTS accesses an Oracle 8
> database. That Oracle 8 database is going to be upgraded to Oracle 9i
soon,
> and I was wondering what I have to do to keep this all running. I think I
> have to upgrade the Oracle client on the Sql Server box to 9i (since the
> Oracle 8 client can not talk to Oracle 9i). Other than that, I am not
aware
> of anything else I have to do.
> Anyone done this before?
> Thanks,
> Michael
database. That Oracle 8 database is going to be upgraded to Oracle 9i soon,
and I was wondering what I have to do to keep this all running. I think I
have to upgrade the Oracle client on the Sql Server box to 9i (since the
Oracle 8 client can not talk to Oracle 9i). Other than that, I am not aware
of anything else I have to do.
Anyone done this before?
Thanks,
Michael
"Snake" wrote:
> I have inherited a Sql Server 2000 instance who's DTS accesses an Oracle 8
> database. That Oracle 8 database is going to be upgraded to Oracle 9i soon,
> and I was wondering what I have to do to keep this all running. I think I
> have to upgrade the Oracle client on the Sql Server box to 9i (since the
> Oracle 8 client can not talk to Oracle 9i). Other than that, I am not aware
> of anything else I have to do.
> Anyone done this before?
> Thanks,
> Michael
|||You should be able to upgrade the Oracle client from 8 to 9i on your side to
solve this problem. My suggestion is to install Oracle 9i on the SQL Server
machine in parallel with the Oracle 8 client. To do this, copy your DTS
package into a new one with a similar name. Create a new DSN that uses the
Oracle 9i client and then test it on the server to make sure the Oracle 9
install worked successfully. Since the Oracle 9i client can read an Oracle 8
database you can switch to this install early and then you'll be prepared
early for the production change on the source database. After the source
database is upgraded to Oracle 9i, you can safely remove the old Oracle 8i
components from your server.
"Snake" wrote:
> I have inherited a Sql Server 2000 instance who's DTS accesses an Oracle 8
> database. That Oracle 8 database is going to be upgraded to Oracle 9i soon,
> and I was wondering what I have to do to keep this all running. I think I
> have to upgrade the Oracle client on the Sql Server box to 9i (since the
> Oracle 8 client can not talk to Oracle 9i). Other than that, I am not aware
> of anything else I have to do.
> Anyone done this before?
> Thanks,
> Michael
|||Also, keep in mind that Oracle's new DATETIME data type has "known" issues
with respect to SQL Server.
Do a search on the net for issues and the workarounds.
Sincerely,
Anthony Thomas
"Amrith" <Amrith@.discussions.microsoft.com> wrote in message
news:5C126AC9-DF98-4B2A-8F8A-E5D887A502AB@.microsoft.com...
You should be able to upgrade the Oracle client from 8 to 9i on your side to
solve this problem. My suggestion is to install Oracle 9i on the SQL Server
machine in parallel with the Oracle 8 client. To do this, copy your DTS
package into a new one with a similar name. Create a new DSN that uses the
Oracle 9i client and then test it on the server to make sure the Oracle 9
install worked successfully. Since the Oracle 9i client can read an Oracle 8
database you can switch to this install early and then you'll be prepared
early for the production change on the source database. After the source
database is upgraded to Oracle 9i, you can safely remove the old Oracle 8i
components from your server.
"Snake" wrote:
> I have inherited a Sql Server 2000 instance who's DTS accesses an Oracle 8
> database. That Oracle 8 database is going to be upgraded to Oracle 9i
soon,
> and I was wondering what I have to do to keep this all running. I think I
> have to upgrade the Oracle client on the Sql Server box to 9i (since the
> Oracle 8 client can not talk to Oracle 9i). Other than that, I am not
aware
> of anything else I have to do.
> Anyone done this before?
> Thanks,
> Michael
DTS connection to Oracle 8; To be upgrated to Oracle 9i. Any guida
I have inherited a Sql Server 2000 instance who's DTS accesses an Oracle 8
database. That Oracle 8 database is going to be upgraded to Oracle 9i soon,
and I was wondering what I have to do to keep this all running. I think I
have to upgrade the Oracle client on the Sql Server box to 9i (since the
Oracle 8 client can not talk to Oracle 9i). Other than that, I am not aware
of anything else I have to do.
Anyone done this before?
Thanks,
MichaelYou should be able to upgrade the Oracle client from 8 to 9i on your side to
solve this problem. My suggestion is to install Oracle 9i on the SQL Server
machine in parallel with the Oracle 8 client. To do this, copy your DTS
package into a new one with a similar name. Create a new DSN that uses the
Oracle 9i client and then test it on the server to make sure the Oracle 9
install worked successfully. Since the Oracle 9i client can read an Oracle 8
database you can switch to this install early and then you'll be prepared
early for the production change on the source database. After the source
database is upgraded to Oracle 9i, you can safely remove the old Oracle 8i
components from your server.
"Snake" wrote:
> I have inherited a Sql Server 2000 instance who's DTS accesses an Oracle 8
> database. That Oracle 8 database is going to be upgraded to Oracle 9i soon,
> and I was wondering what I have to do to keep this all running. I think I
> have to upgrade the Oracle client on the Sql Server box to 9i (since the
> Oracle 8 client can not talk to Oracle 9i). Other than that, I am not aware
> of anything else I have to do.
> Anyone done this before?
> Thanks,
> Michael|||"Snake" wrote:
> I have inherited a Sql Server 2000 instance who's DTS accesses an Oracle 8
> database. That Oracle 8 database is going to be upgraded to Oracle 9i soon,
> and I was wondering what I have to do to keep this all running. I think I
> have to upgrade the Oracle client on the Sql Server box to 9i (since the
> Oracle 8 client can not talk to Oracle 9i). Other than that, I am not aware
> of anything else I have to do.
> Anyone done this before?
> Thanks,
> Michael|||Also, keep in mind that Oracle's new DATETIME data type has "known" issues
with respect to SQL Server.
Do a search on the net for issues and the workarounds.
Sincerely,
Anthony Thomas
"Amrith" <Amrith@.discussions.microsoft.com> wrote in message
news:5C126AC9-DF98-4B2A-8F8A-E5D887A502AB@.microsoft.com...
You should be able to upgrade the Oracle client from 8 to 9i on your side to
solve this problem. My suggestion is to install Oracle 9i on the SQL Server
machine in parallel with the Oracle 8 client. To do this, copy your DTS
package into a new one with a similar name. Create a new DSN that uses the
Oracle 9i client and then test it on the server to make sure the Oracle 9
install worked successfully. Since the Oracle 9i client can read an Oracle 8
database you can switch to this install early and then you'll be prepared
early for the production change on the source database. After the source
database is upgraded to Oracle 9i, you can safely remove the old Oracle 8i
components from your server.
"Snake" wrote:
> I have inherited a Sql Server 2000 instance who's DTS accesses an Oracle 8
> database. That Oracle 8 database is going to be upgraded to Oracle 9i
soon,
> and I was wondering what I have to do to keep this all running. I think I
> have to upgrade the Oracle client on the Sql Server box to 9i (since the
> Oracle 8 client can not talk to Oracle 9i). Other than that, I am not
aware
> of anything else I have to do.
> Anyone done this before?
> Thanks,
> Michael
database. That Oracle 8 database is going to be upgraded to Oracle 9i soon,
and I was wondering what I have to do to keep this all running. I think I
have to upgrade the Oracle client on the Sql Server box to 9i (since the
Oracle 8 client can not talk to Oracle 9i). Other than that, I am not aware
of anything else I have to do.
Anyone done this before?
Thanks,
MichaelYou should be able to upgrade the Oracle client from 8 to 9i on your side to
solve this problem. My suggestion is to install Oracle 9i on the SQL Server
machine in parallel with the Oracle 8 client. To do this, copy your DTS
package into a new one with a similar name. Create a new DSN that uses the
Oracle 9i client and then test it on the server to make sure the Oracle 9
install worked successfully. Since the Oracle 9i client can read an Oracle 8
database you can switch to this install early and then you'll be prepared
early for the production change on the source database. After the source
database is upgraded to Oracle 9i, you can safely remove the old Oracle 8i
components from your server.
"Snake" wrote:
> I have inherited a Sql Server 2000 instance who's DTS accesses an Oracle 8
> database. That Oracle 8 database is going to be upgraded to Oracle 9i soon,
> and I was wondering what I have to do to keep this all running. I think I
> have to upgrade the Oracle client on the Sql Server box to 9i (since the
> Oracle 8 client can not talk to Oracle 9i). Other than that, I am not aware
> of anything else I have to do.
> Anyone done this before?
> Thanks,
> Michael|||"Snake" wrote:
> I have inherited a Sql Server 2000 instance who's DTS accesses an Oracle 8
> database. That Oracle 8 database is going to be upgraded to Oracle 9i soon,
> and I was wondering what I have to do to keep this all running. I think I
> have to upgrade the Oracle client on the Sql Server box to 9i (since the
> Oracle 8 client can not talk to Oracle 9i). Other than that, I am not aware
> of anything else I have to do.
> Anyone done this before?
> Thanks,
> Michael|||Also, keep in mind that Oracle's new DATETIME data type has "known" issues
with respect to SQL Server.
Do a search on the net for issues and the workarounds.
Sincerely,
Anthony Thomas
"Amrith" <Amrith@.discussions.microsoft.com> wrote in message
news:5C126AC9-DF98-4B2A-8F8A-E5D887A502AB@.microsoft.com...
You should be able to upgrade the Oracle client from 8 to 9i on your side to
solve this problem. My suggestion is to install Oracle 9i on the SQL Server
machine in parallel with the Oracle 8 client. To do this, copy your DTS
package into a new one with a similar name. Create a new DSN that uses the
Oracle 9i client and then test it on the server to make sure the Oracle 9
install worked successfully. Since the Oracle 9i client can read an Oracle 8
database you can switch to this install early and then you'll be prepared
early for the production change on the source database. After the source
database is upgraded to Oracle 9i, you can safely remove the old Oracle 8i
components from your server.
"Snake" wrote:
> I have inherited a Sql Server 2000 instance who's DTS accesses an Oracle 8
> database. That Oracle 8 database is going to be upgraded to Oracle 9i
soon,
> and I was wondering what I have to do to keep this all running. I think I
> have to upgrade the Oracle client on the Sql Server box to 9i (since the
> Oracle 8 client can not talk to Oracle 9i). Other than that, I am not
aware
> of anything else I have to do.
> Anyone done this before?
> Thanks,
> Michael
Subscribe to:
Posts (Atom)