DTS

Hi,
When i save a DTS package within msdb i must provide a
valid login to save it. If i schedule the package with the
DTS schedule options (right click on the DTS object), it
will create a job with a dtsrun step with the login and
password, that i provided when it was saved, encrypted for
load the DTS. I'm i right '
Suppose i save the package with dtsadmin user, where can i
found the information about the user that saved the
package ' i need this info ' suppose i change the user's
password, my job will not run any more until i rebuild the
DTSrun encrytion with the new password.
Thanks
PhilNot exactly. The package is saved with an owner who is the
logged in user who created the package. You do not have to
provide any information to save a package.
If you schedule it through Enterprise Manager, it is
scheduled with the currently logged in users credentials.
The owner and the credentials used when scheduling the
package can be different. Additionally, if it's all done
through Windows authentication, you wouldn't have a user id
and password.
The user and password used in the encrypted string for
dtsrun is not stored anywhere.
In terms of changing passwords, that's part of the reason
that Windows authentication is preferred. The biggest reason
is that it's more secure but it also often eliminates
maintenance issues such as this.
-Sue
On Fri, 2 Apr 2004 09:37:34 -0800, "Phil"
<anonymous@.discussions.microsoft.com> wrote:

>Hi,
>When i save a DTS package within msdb i must provide a
>valid login to save it. If i schedule the package with the
>DTS schedule options (right click on the DTS object), it
>will create a job with a dtsrun step with the login and
>password, that i provided when it was saved, encrypted for
>load the DTS. I'm i right '
>Suppose i save the package with dtsadmin user, where can i
>found the information about the user that saved the
>package ' i need this info ' suppose i change the user's
>password, my job will not run any more until i rebuild the
>DTSrun encrytion with the new password.
>Thanks
>Phil

DSN vs login authentication

Hello everybody!
I've created a DSN from a WIN2K Pro client to connect to a SQL Server 7.0
running on a WIN2K Server with domain controller.
The SQL Server authentication mode on the server machine is "Mixed mode"
Inside the client DSN configuration I've specified that the Authentication
Mode is SQL Server Mode, so I've entered the correct values for Access Id
and Password (I've already tested them connecting directly on the server
machine from query analyzer).
If I test this DSN connection everything works fine.
But if I run my VisualFoxPro Application (that use surely the DSN I've set
up) and appears the "sql server connection dialog box" when I click on "Ok"
I obtain the following error:
...
[Microsoft]ODBC-SQL Server Drive][Sql Server][Login failed for u
ser "server
name/user"]
as the Authentication Mode was "Windows" (trusted connection) and not "SQL
Server" as truly is.
Note that on the same network I've others WIN2K box with the same setup
(same MDAC 2.6, same domain user properties, same DSN setup) and for them I
don't have any problems.
Is there a way to force the connection process from the client to the server
to use always "SQL server authentication mode" (if DSN is not enough)?!?!
Can anyone help me? Thanks in advance!
Riccardo Piccini
Supporto Software
EDP SERVICE SRLCheck the version of the SQL Server ODBC driver on the client machine. It
sounds like you are running into a problem with sqlsrv32.dll version
2000.80.194. This version ignores SQL authentication and uses NT
authentication. The only way to resolve the problem is to upgrade teh
version of MDAC. I believe the problem was resolved in MDAC 2.6 SP2.
Rand
This posting is provided "as is" with no warranties and confers no rights.

DSN vs login authentication

Hello everybody!
I've created a DSN from a WIN2K Pro client to connect to a SQL Server 7.0
running on a WIN2K Server with domain controller.
The SQL Server authentication mode on the server machine is "Mixed mode"
Inside the client DSN configuration I've specified that the Authentication
Mode is SQL Server Mode, so I've entered the correct values for Access Id
and Password (I've already tested them connecting directly on the server
machine from query analyzer).
If I test this DSN connection everything works fine.
But if I run my VisualFoxPro Application (that use surely the DSN I've set
up) and appears the "sql server connection dialog box" when I click on "Ok"
I obtain the following error:
...
[Microsoft]ODBC-SQL Server Drive][Sql Server][Login failed for user "server
name/user"]
as the Authentication Mode was "Windows" (trusted connection) and not "SQL
Server" as truly is.
Note that on the same network I've others WIN2K box with the same setup
(same MDAC 2.6, same domain user properties, same DSN setup) and for them I
don't have any problems.
Is there a way to force the connection process from the client to the server
to use always "SQL server authentication mode" (if DSN is not enough)?!?!
Can anyone help me? Thanks in advance!
Riccardo Piccini
Supporto Software
EDP SERVICE SRL
Check the version of the SQL Server ODBC driver on the client machine. It
sounds like you are running into a problem with sqlsrv32.dll version
2000.80.194. This version ignores SQL authentication and uses NT
authentication. The only way to resolve the problem is to upgrade teh
version of MDAC. I believe the problem was resolved in MDAC 2.6 SP2.
Rand
This posting is provided "as is" with no warranties and confers no rights.