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

saving a trace to table in SQL Profiler

Hi All,
On Trace Properties General tab of SQL Server 2000, there
is a check box setting for saving a trace to a table. The
trace properties dialog box asks for the name of the
table, thus I am assuming first, I must create the table.
The question is how do i figure out how many columns and
what column names i should have in this table in which i
am going to save the trace.
Thanks,
Mitra
There is no need to create the table first. Profiler will create the table
for you. The table that is created has one column for data column you
select in you profiler session, plus it adds and identity column.
----
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"Mitra Fatholahi" <mitra928@.hotmail.com> wrote in message
news:12bf701c4433f$6d5f76b0$a401280a@.phx.gbl...
> Hi All,
> On Trace Properties General tab of SQL Server 2000, there
> is a check box setting for saving a trace to a table. The
> trace properties dialog box asks for the name of the
> table, thus I am assuming first, I must create the table.
> The question is how do i figure out how many columns and
> what column names i should have in this table in which i
> am going to save the trace.
> Thanks,
> Mitra
|||Mitra,
And as a For What It Is Worth: If you save the trace into a file and later
want to load a table, the fn_trace_gettable also creates the table for you.
This approach has the advantage of not putting the load of inserting tables
rows on the server and the disadvantage that you cannot query the trace data
until after the file is closed. (But this is usually fine for analyzing
problems.)
Russell Fields
"Mitra Fatholahi" <mitra928@.hotmail.com> wrote in message
news:12bf701c4433f$6d5f76b0$a401280a@.phx.gbl...
> Hi All,
> On Trace Properties General tab of SQL Server 2000, there
> is a check box setting for saving a trace to a table. The
> trace properties dialog box asks for the name of the
> table, thus I am assuming first, I must create the table.
> The question is how do i figure out how many columns and
> what column names i should have in this table in which i
> am going to save the trace.
> Thanks,
> Mitra
sql

saving a trace to table in SQL Profiler

Hi All,
On Trace Properties General tab of SQL Server 2000, there
is a check box setting for saving a trace to a table. The
trace properties dialog box asks for the name of the
table, thus I am assuming first, I must create the table.
The question is how do i figure out how many columns and
what column names i should have in this table in which i
am going to save the trace.
Thanks,
MitraThere is no need to create the table first. Profiler will create the table
for you. The table that is created has one column for data column you
select in you profiler session, plus it adds and identity column.
--
----
----
--
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"Mitra Fatholahi" <mitra928@.hotmail.com> wrote in message
news:12bf701c4433f$6d5f76b0$a401280a@.phx.gbl...
> Hi All,
> On Trace Properties General tab of SQL Server 2000, there
> is a check box setting for saving a trace to a table. The
> trace properties dialog box asks for the name of the
> table, thus I am assuming first, I must create the table.
> The question is how do i figure out how many columns and
> what column names i should have in this table in which i
> am going to save the trace.
> Thanks,
> Mitra|||Mitra,
And as a For What It Is Worth: If you save the trace into a file and later
want to load a table, the fn_trace_gettable also creates the table for you.
This approach has the advantage of not putting the load of inserting tables
rows on the server and the disadvantage that you cannot query the trace data
until after the file is closed. (But this is usually fine for analyzing
problems.)
Russell Fields
"Mitra Fatholahi" <mitra928@.hotmail.com> wrote in message
news:12bf701c4433f$6d5f76b0$a401280a@.phx.gbl...
> Hi All,
> On Trace Properties General tab of SQL Server 2000, there
> is a check box setting for saving a trace to a table. The
> trace properties dialog box asks for the name of the
> table, thus I am assuming first, I must create the table.
> The question is how do i figure out how many columns and
> what column names i should have in this table in which i
> am going to save the trace.
> Thanks,
> Mitra

saving a trace to table in SQL Profiler

Hi All,
On Trace Properties General tab of SQL Server 2000, there
is a check box setting for saving a trace to a table. The
trace properties dialog box asks for the name of the
table, thus I am assuming first, I must create the table.
The question is how do i figure out how many columns and
what column names i should have in this table in which i
am going to save the trace.
Thanks,
MitraThere is no need to create the table first. Profiler will create the table
for you. The table that is created has one column for data column you
select in you profiler session, plus it adds and identity column.
----
----
--
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"Mitra Fatholahi" <mitra928@.hotmail.com> wrote in message
news:12bf701c4433f$6d5f76b0$a401280a@.phx
.gbl...
> Hi All,
> On Trace Properties General tab of SQL Server 2000, there
> is a check box setting for saving a trace to a table. The
> trace properties dialog box asks for the name of the
> table, thus I am assuming first, I must create the table.
> The question is how do i figure out how many columns and
> what column names i should have in this table in which i
> am going to save the trace.
> Thanks,
> Mitra|||Mitra,
And as a For What It Is Worth: If you save the trace into a file and later
want to load a table, the fn_trace_gettable also creates the table for you.
This approach has the advantage of not putting the load of inserting tables
rows on the server and the disadvantage that you cannot query the trace data
until after the file is closed. (But this is usually fine for analyzing
problems.)
Russell Fields
"Mitra Fatholahi" <mitra928@.hotmail.com> wrote in message
news:12bf701c4433f$6d5f76b0$a401280a@.phx
.gbl...
> Hi All,
> On Trace Properties General tab of SQL Server 2000, there
> is a check box setting for saving a trace to a table. The
> trace properties dialog box asks for the name of the
> table, thus I am assuming first, I must create the table.
> The question is how do i figure out how many columns and
> what column names i should have in this table in which i
> am going to save the trace.
> Thanks,
> Mitra

SAve SQLMaint jobs to a central server

When setting up a maintenance plan through the wizard, there is the option to
select a remote server to receive the job history. However, this option does
not seem available when using SqlMaint to setup jobs. I have a setup where 8
remote servers are setup with one central MSX server. Unfortunately, I can't
figure out how to save the job history to the central MSX server and not to
the local servers. Anyone know how the maintenance plan wizard sets things
up to save job histories remotely?
Thanks,
Alex Gadea
I don't think that it is the job history which is written to the remote server, it is only the maint
plan history table(s). I might be wrong, of course...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Alex" <Alex@.discussions.microsoft.com> wrote in message
news:46236FC9-AB41-43D6-AE75-4715B66F6267@.microsoft.com...
> When setting up a maintenance plan through the wizard, there is the option to
> select a remote server to receive the job history. However, this option does
> not seem available when using SqlMaint to setup jobs. I have a setup where 8
> remote servers are setup with one central MSX server. Unfortunately, I can't
> figure out how to save the job history to the central MSX server and not to
> the local servers. Anyone know how the maintenance plan wizard sets things
> up to save job histories remotely?
> Thanks,
> Alex Gadea

SAve SQLMaint jobs to a central server

When setting up a maintenance plan through the wizard, there is the option t
o
select a remote server to receive the job history. However, this option doe
s
not seem available when using SqlMaint to setup jobs. I have a setup where
8
remote servers are setup with one central MSX server. Unfortunately, I can'
t
figure out how to save the job history to the central MSX server and not to
the local servers. Anyone know how the maintenance plan wizard sets things
up to save job histories remotely?
Thanks,
Alex GadeaI don't think that it is the job history which is written to the remote serv
er, it is only the maint
plan history table(s). I might be wrong, of course...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Alex" <Alex@.discussions.microsoft.com> wrote in message
news:46236FC9-AB41-43D6-AE75-4715B66F6267@.microsoft.com...
> When setting up a maintenance plan through the wizard, there is the option
to
> select a remote server to receive the job history. However, this option d
oes
> not seem available when using SqlMaint to setup jobs. I have a setup wher
e 8
> remote servers are setup with one central MSX server. Unfortunately, I ca
n't
> figure out how to save the job history to the central MSX server and not t
o
> the local servers. Anyone know how the maintenance plan wizard sets thing
s
> up to save job histories remotely?
> Thanks,
> Alex Gadea

SAve SQLMaint jobs to a central server

When setting up a maintenance plan through the wizard, there is the option to
select a remote server to receive the job history. However, this option does
not seem available when using SqlMaint to setup jobs. I have a setup where 8
remote servers are setup with one central MSX server. Unfortunately, I can't
figure out how to save the job history to the central MSX server and not to
the local servers. Anyone know how the maintenance plan wizard sets things
up to save job histories remotely?
Thanks,
Alex GadeaI don't think that it is the job history which is written to the remote server, it is only the maint
plan history table(s). I might be wrong, of course...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Alex" <Alex@.discussions.microsoft.com> wrote in message
news:46236FC9-AB41-43D6-AE75-4715B66F6267@.microsoft.com...
> When setting up a maintenance plan through the wizard, there is the option to
> select a remote server to receive the job history. However, this option does
> not seem available when using SqlMaint to setup jobs. I have a setup where 8
> remote servers are setup with one central MSX server. Unfortunately, I can't
> figure out how to save the job history to the central MSX server and not to
> the local servers. Anyone know how the maintenance plan wizard sets things
> up to save job histories remotely?
> Thanks,
> Alex Gadea