I have a SSIS package used the protection level as "DontSaveSensitive"
So initially I have saved the oledb connection manager password as in a XML config file. And this worked fine for me.
Now for business requirement I have stored the configuration in SQL Server.
Including password.
Initially it worked fine.But suddenly connection manager is not taking password from sqlDB.
If I set an environment variable for the "password" it's working.
My question is:
what is the solution for this. (I can only save the configurations in SQL)
initially how it worked. I mean initially from SQL Server the password was taking.
Please give some clue. I am doing a lot of trial and error.
How are you going to retrieve the password from the database if you need the password to connect the database?
There is a small article here about storing passwords which may help you.
Related
I made an SSIS package that exports data from Microsoft SQL Server and imports it into a .csv and mysql file. I start to use proxy account and it work, but only when user is logged. How make it works when user is logged off !? Thank you in advance.
I solved this problem. Firstly, created System DSN.
link for this
Does any connection manager in the package use ODBC DSN? If any ODBC
DSN is used, please make sure the DSN type is System DSN rather than
User DSN. The user DSN may not be accessible when the user that create
the DSN logs off.
Secondly, create new proxy and give him credentials
link for this
Use master
CREATE CREDENTIAL [MyCredential] WITH IDENTITY = 'yourdomain\myWindowAccount', secret = 'WindowLoginPassword'
Use msdb
Sp_add_proxy #proxy_name='MyProxy', #credential_name='MyCredential'
Sp_grant_login_to_proxy #login_name=' devlogin', #proxy_name='MyProxy'
Sp_grant_proxy_to_subsystem #proxy_name='MyProxy', #subsystem_name='SSIS'
I have scenario where I have several variables eg. sourceFilePath, sourceFileName and etc. I am storing the variables as a configurations in SQL Server Table. To store this configuration, we have to provide a connection (I have opted for OLEDB Connection).
When I am executing this from BIDS, it is working very fine and there are no issues at all.
I can change the sourceFilePath and sourceFileName from the Configuration table and the package is taking the changed path as well.
But the problem arrived when I have deployed the Package on SQL Server. I am not able to get the configuration values from table and it keeps on saying "Login failed from user.... Unable to load the configuration ...... ".
What can I do to avoide this situation?
Yes, I tried giving the password explicitly when scheduling the job but I can do the same for production server as it stores the password as a plain text.
Any help is highly appreciated.
Many thanks.
Thanks to all. I just need to set ProtectionLevel property for my packages and the rest is done. Such a small thing and it was making me nuts...
I have an SSIS package that I'm trying to run from a SQL job. However, it fails, and the log claims that the password for the user specified in the connection string is wrong. For testing I've got the protection level set to EncryptSensitiveWithKey, and it runs fine from BIDS. When I import it into SSIS I change it to ServerStorage. (My understanding of the documentation says that this should work. I could be wrong though.) During the import it asks for the decryption key, which I supply, and everything seems fine.
It also seems fine when I set up the job in SQL Server Agent. However, when I run the job, it fails and the log says that the password for that user is incorrect. It doesn't say that there is a permission problem, but that the password is wrong.
I've been through the connections and double checked the username and password that is used to access the database. I can connect just fine with that username and password combination. This is the user that is used to connect to the database. There don't appear to be any problems executing the job.
Any help with this would be appreciated.
From what it looks like, it seems like you still need to modify the password after you have installed it to the SQL Agent. The decryption key decrypts the sensitive information but it is still tied to the person that created it. Have you tried re-entering the password when you install it to the server?
http://decipherinfosys.wordpress.com/2008/09/17/scheduling-ssis-packages-with-sql-server-agent/
I'm trying to use Sam Saffron's program SoSlow (as suggested here) for importing SO's data sump into MS SQL Server 2008.
Unfortunately, I have little idea of what I'm doing, and so do not know the Connection String that the program asks for.
I have tried the following syntax:
Data Source=SHIMI\SQLEXPRESS; Initial Catalog=SO; User Id=sa; Password=;
where SHIMI is the name of my machine, and SO is the name of the DB I've created.
SoSlow announces that the login fails "Login failed for user 'sa'".
Tried all other logins that are listed through the object browser in SQL Server Management Studio > Security > logins.
I have not altered the server in any way since install, defaults apply.
What am I doing wrong? (besides asking noob questions)
Thanks!
You would have set an SA password during the installation of SQL Server Express - if you don't recall it you will need to reset it. Follow the steps here to reset.
Mysql odbc connection string is stored in the windows registry as plain text. So someone can find it and view my database.
How can I sort out this security problem.
thanks
UPDATE:
Thanks for your response. The server is set-up in a very secure way e.g SSL for FTP and two factor authentication for Remote desktop. But the problem is if somebody does get onto the server, they can see the password for the database login.
I was thinking about encrypting the password within the DNSless string and having a key in a external file to unecrypt it. But the problem still remains if someone finds the key they can get the password.
Do you have any other suggestions?
you can set permissions on Windows Registry key folders (XP) to deny access to users and groups. Right-click the item in the folder panel and select "Permissions..."
good luck MikeD