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 |
|
SamC
White Water Yakist
3467 Posts |
 Posted - 2005-06-02 : 21:51:33
|
quote:
BOL
A tilde (~) character after the forward slash (for example, /~Z) indicates that the parameter value is encrypted and what follows is the hexadecimal text of the encrypted value.
Where's the how-to documentation on encrypting parameters? |
|
|
Merkin
Funky Drop Bear Fearing SQL Dude!
4970 Posts |
Posted - 2005-06-03 : 01:39:48
|
| Create a DTS package, and right click to schedule it.Open up the scheduled job step and have a look at the command that is run.DamianIta erat quando hic adveni. |
 |
|
|
SamC
White Water Yakist
3467 Posts |
Posted - 2005-06-03 : 08:27:56
|
quote:
Originally posted by Merkin
Create a DTS package, and right click to schedule it.Open up the scheduled job step and have a look at the command that is run.
This only shows that EM knows how to encrypt parameters. For those of us that hand-code dtsrun commands, BOL emphasizes that parameters containing sensitive information (username/password) can be encrypted. But BOL doesn't let on how to get the encryption done. |
|
|
|
Merkin
Funky Drop Bear Fearing SQL Dude!
4970 Posts |
Posted - 2005-06-03 : 09:54:55
|
BOL says that they are encrypted using SQL Server encryption. So, at a guess... use the SQL Server Encrypt() function to encrypt the parameters. I'm not sure whether that means the entire string i.e.Select encrypt('/Sserver_name /Uuser_nName /Ppassword /Npackage_name /Mpackage_password')Or individual params. You can experiment and post the result here.... it's friday night, I just got home, and I don't feel like doing it myself   DamianIta erat quando hic adveni. |
|
|
|
SamC
White Water Yakist
3467 Posts |
Posted - 2005-06-03 : 10:38:55
|
| I'll check this out and post back. |
|
|
|
|
|
|
Encrypting dtsrun parameters