Showing posts with label connection. Show all posts
Showing posts with label connection. Show all posts

Friday, March 30, 2012

Saving SSIS package connection passwords

Hello All,

I'm new to SQL 2005. I am setting up some SSIS packages which will connect to an Oracle database and copy some tables from it. These packages will then be scheduled to run on a daily basis. Because they will run automatically, it is required that passwords be saved along with the connection string. However, even though the password is saved (and encrypted, I checked the .dtsx in notepad), when I run the package, the connection to Oracle fails. Only if I respecify the password does it run correctly. How can I correctly save this password so that I can schedule automatic execution? Thanks for any info.

If you search this forum for "connection password" you'll get plenty of results. Basically, SSIS does not save passwords in connection strings.

Verify that your package property, ProtectionLevel, is set to EncryptSensitiveWithUserKey. If that doesn't work, then you can put the connection string for the Oracle database in a configuration file, of which you can manually update to contain the password. All of this is posted throughout this forum.|||

Hi,

Thanks for your reply. The thing about that is, that the package is owned by the OS user I use, but the Server Agent runs on another profile (System), so encrypting with a user key will make the Agent unable to execute de package. I wil check out the configuratio file thing, though.

|||Then you can do EncryptSensitiveWithPassword and specify the package password in SQL Agent by altering the dtexec command line parameters.|||I ran into your problem and my solution was to change the CreatorName property of the package to the account that SQL Agent runs under, and I also changed the CreatorComputerName to the name of the production server, then it finally workedsql

Wednesday, March 28, 2012

Saving ODBC password

I have an app that uses ODBC for connection. Everytime the users log in it prompts the user to enter a password.

Is there any way (reg key entery ?) for the password to be saved so the user is not prompted?

Thanks

MPM

No, I'm sorry you can't do that. This is a security issue, since someone may gain access to your registry information, and thereby uncover your password. Even if you modified your registry information to store the password ODBC would not read that information.

I can't think of a work-around, unless you had a VB script or something that automatically logged on to a database? Perhaps you could use trusted connection instead of UserID/Password connection?

Hope this helps.

~Warren

|||There is no way to save the ODBC password in the registery. But you can do somethings to avoid this.

1. If you have a logon screen in your app. You can use the same password to get access to your app and to get access to your DB. If you do that you can just store the user/pass used to get access to the app and use it for the ODBC.
2. You can use trusted connection if you are using a Domain Controller, this is the easiest way.
3. You can code a box that opens instead of the default ODBC password request box and store the password in a MDB file.

Here's my suggestions.

Regards

JBsql

Saving ODBC password

I have an app that uses ODBC for connection. Everytime the users log in it prompts the user to enter a password.

Is there any way (reg key entery ?) for the password to be saved so the user is not prompted?

Thanks

MPM

No, I'm sorry you can't do that. This is a security issue, since someone may gain access to your registry information, and thereby uncover your password. Even if you modified your registry information to store the password ODBC would not read that information.

I can't think of a work-around, unless you had a VB script or something that automatically logged on to a database? Perhaps you could use trusted connection instead of UserID/Password connection?

Hope this helps.

~Warren

|||There is no way to save the ODBC password in the registery. But you can do somethings to avoid this.

1. If you have a logon screen in your app. You can use the same password to get access to your app and to get access to your DB. If you do that you can just store the user/pass used to get access to the app and use it for the ODBC.
2. You can use trusted connection if you are using a Domain Controller, this is the easiest way.
3. You can code a box that opens instead of the default ODBC password request box and store the password in a MDB file.

Here's my suggestions.

Regards

JB

Friday, March 23, 2012

Saving Auto Recovery Information

Hi

I am using the Microsoft SQL Server Management Studio to manage our database objects over a VPN connection. At scheduled intervals the system saves recovery information.

The problem is that the location of the recovery files appears to be located on a remote server. This causes the UI to completely freeze while the operation is in progress.

How can I change the location of the recovery files or turn off the Auto Recovery functionality completely.

In VS2005 this is configurable in the Tools-->Options-->Environment settings.

Thanks.

There is not configurable today in SQL 2005. We have a tracking bug for this issue.

Thanks,

Gops Dwarak

|||

Thanks for the reply.

Do you know when a fix may be released for this? Are you aware of how I can get the Enterprise Manager working on the same pc as the SQL Server Management Studio or do I need to uninstall SQL Server 2005?

Regards

David

|||

Enterprise manager and SQL Server Management studio can be run side by side on the same box. Answer is, you do not need to uninstall SQL 2005 to get Enterprise Manger working.

On the fix for the Autorecovery, it is planned to be fixed in next service pack. We are in planning stage for next service pack and to not have dates for this release now.

Thanks,

Gops Dwarak, MSFT

|||

I haven't tried this but this registry mod should disable AutoRecovery. If it doesn't work let me know and I'll dig a bit deeper. All the standard disclaimers about registry manipulation apply.

Go to HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL Server\90\Tools\Shell\General\AutoRecover and change the “AutoRecover Enabled” value to zero.

|||

Bruce,

I have tried your fix on an XP SP2 machine and it seems to have worked. The only thing was that the reg key path for me (using SQL Server Management Studio Express) was:

HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL Server\90\Tools\ShellSEM\General\AutoRecover

Thanks.

|||

Hi everybody.

I'm having the same problem in Microsoft Visual Studio 2005, Version 8.0.50727.42 (RTM.050727-4200)
Microsoft .NET Framework Version 2.0.50727 but not only the IDE freezes when saving autorecovery information but also when saving any modified file.

Do you guys know of a thread like this related to this issue? Any ideas?

Thanks a lot!

|||

Hi,

I have the same problem.

There is a conflict between the antivirus and the source control.

I did not find a solution yet. Does somebody have an idea?

Thanks.

Saving Auto Recovery Information

Hi

I am using the Microsoft SQL Server Management Studio to manage our database objects over a VPN connection. At scheduled intervals the system saves recovery information.

The problem is that the location of the recovery files appears to be located on a remote server. This causes the UI to completely freeze while the operation is in progress.

How can I change the location of the recovery files or turn off the Auto Recovery functionality completely.

In VS2005 this is configurable in the Tools-->Options-->Environment settings.

Thanks.

There is not configurable today in SQL 2005. We have a tracking bug for this issue.

Thanks,

Gops Dwarak

|||

Thanks for the reply.

Do you know when a fix may be released for this? Are you aware of how I can get the Enterprise Manager working on the same pc as the SQL Server Management Studio or do I need to uninstall SQL Server 2005?

Regards

David

|||

Enterprise manager and SQL Server Management studio can be run side by side on the same box. Answer is, you do not need to uninstall SQL 2005 to get Enterprise Manger working.

On the fix for the Autorecovery, it is planned to be fixed in next service pack. We are in planning stage for next service pack and to not have dates for this release now.

Thanks,

Gops Dwarak, MSFT

|||

I haven't tried this but this registry mod should disable AutoRecovery. If it doesn't work let me know and I'll dig a bit deeper. All the standard disclaimers about registry manipulation apply.

Go to HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL Server\90\Tools\Shell\General\AutoRecover and change the “AutoRecover Enabled” value to zero.

|||

Bruce,

I have tried your fix on an XP SP2 machine and it seems to have worked. The only thing was that the reg key path for me (using SQL Server Management Studio Express) was:

HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL Server\90\Tools\ShellSEM\General\AutoRecover

Thanks.

|||

Hi everybody.

I'm having the same problem in Microsoft Visual Studio 2005, Version 8.0.50727.42 (RTM.050727-4200)
Microsoft .NET Framework Version 2.0.50727 but not only the IDE freezes when saving autorecovery information but also when saving any modified file.

Do you guys know of a thread like this related to this issue? Any ideas?

Thanks a lot!

|||

Hi,

I have the same problem.

There is a conflict between the antivirus and the source control.

I did not find a solution yet. Does somebody have an idea?

Thanks.

sql

Saving Auto Recovery Information

Hi

I am using the Microsoft SQL Server Management Studio to manage our database objects over a VPN connection. At scheduled intervals the system saves recovery information.

The problem is that the location of the recovery files appears to be located on a remote server. This causes the UI to completely freeze while the operation is in progress.

How can I change the location of the recovery files or turn off the Auto Recovery functionality completely.

In VS2005 this is configurable in the Tools-->Options-->Environment settings.

Thanks.

There is not configurable today in SQL 2005. We have a tracking bug for this issue.

Thanks,

Gops Dwarak

|||

Thanks for the reply.

Do you know when a fix may be released for this? Are you aware of how I can get the Enterprise Manager working on the same pc as the SQL Server Management Studio or do I need to uninstall SQL Server 2005?

Regards

David

|||

Enterprise manager and SQL Server Management studio can be run side by side on the same box. Answer is, you do not need to uninstall SQL 2005 to get Enterprise Manger working.

On the fix for the Autorecovery, it is planned to be fixed in next service pack. We are in planning stage for next service pack and to not have dates for this release now.

Thanks,

Gops Dwarak, MSFT

|||

I haven't tried this but this registry mod should disable AutoRecovery. If it doesn't work let me know and I'll dig a bit deeper. All the standard disclaimers about registry manipulation apply.

Go to HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL Server\90\Tools\Shell\General\AutoRecover and change the “AutoRecover Enabled” value to zero.

|||

Bruce,

I have tried your fix on an XP SP2 machine and it seems to have worked. The only thing was that the reg key path for me (using SQL Server Management Studio Express) was:

HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL Server\90\Tools\ShellSEM\General\AutoRecover

Thanks.

|||

Hi everybody.

I'm having the same problem in Microsoft Visual Studio 2005, Version 8.0.50727.42 (RTM.050727-4200)
Microsoft .NET Framework Version 2.0.50727 but not only the IDE freezes when saving autorecovery information but also when saving any modified file.

Do you guys know of a thread like this related to this issue? Any ideas?

Thanks a lot!

|||

Hi,

I have the same problem.

There is a conflict between the antivirus and the source control.

I did not find a solution yet. Does somebody have an idea?

Thanks.

Saving Auto Recovery Information

Hi

I am using the Microsoft SQL Server Management Studio to manage our database objects over a VPN connection. At scheduled intervals the system saves recovery information.

The problem is that the location of the recovery files appears to be located on a remote server. This causes the UI to completely freeze while the operation is in progress.

How can I change the location of the recovery files or turn off the Auto Recovery functionality completely.

In VS2005 this is configurable in the Tools-->Options-->Environment settings.

Thanks.

There is not configurable today in SQL 2005. We have a tracking bug for this issue.

Thanks,

Gops Dwarak

|||

Thanks for the reply.

Do you know when a fix may be released for this? Are you aware of how I can get the Enterprise Manager working on the same pc as the SQL Server Management Studio or do I need to uninstall SQL Server 2005?

Regards

David

|||

Enterprise manager and SQL Server Management studio can be run side by side on the same box. Answer is, you do not need to uninstall SQL 2005 to get Enterprise Manger working.

On the fix for the Autorecovery, it is planned to be fixed in next service pack. We are in planning stage for next service pack and to not have dates for this release now.

Thanks,

Gops Dwarak, MSFT

|||

I haven't tried this but this registry mod should disable AutoRecovery. If it doesn't work let me know and I'll dig a bit deeper. All the standard disclaimers about registry manipulation apply.

Go to HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL Server\90\Tools\Shell\General\AutoRecover and change the “AutoRecover Enabled” value to zero.

|||

Bruce,

I have tried your fix on an XP SP2 machine and it seems to have worked. The only thing was that the reg key path for me (using SQL Server Management Studio Express) was:

HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL Server\90\Tools\ShellSEM\General\AutoRecover

Thanks.

|||

Hi everybody.

I'm having the same problem in Microsoft Visual Studio 2005, Version 8.0.50727.42 (RTM.050727-4200)
Microsoft .NET Framework Version 2.0.50727 but not only the IDE freezes when saving autorecovery information but also when saving any modified file.

Do you guys know of a thread like this related to this issue? Any ideas?

Thanks a lot!

|||

Hi,

I have the same problem.

There is a conflict between the antivirus and the source control.

I did not find a solution yet. Does somebody have an idea?

Thanks.

Wednesday, March 7, 2012

SAP connection

Hi everyone,

We are trying to send data from SQL into SAP-BW as far as We are it look like every thing is set at SAP side but We can't send data. Does any one has information about what should I set in SQL side? because all the information that SAP people konw is that I have to create a user in SQL but they don't know any thing about the security.

Thanks.

What are you doing for it? You use RFC Connection to SAP? Or you use ABAP program for retrieve data from SQL server?

|||

Hi,

I'm using RFC via SAP DB Connector, I set the information at SAP side to connect to SQL and it's working fine I can see tables and it's data with in the SAP data source builder but when I try to upload data into an infoobject I can't read any data SAP sends the message no idoc read from source system.

Thanks for your help.