URGENT!!!! SSIS Configurations And SQL Jobs
May 11, 2006
Hi there,
I've got an urgent thing I need to resolve.
I have a package that has a file connection. We have set the connection in the package for development - we also have the connection in a config file.
We are calling the package from SQL Jobs. In the step we call the package in, we try to set the value for the connection in the Data Source tab. However, the package does NOT use the value we enter.
I then removed the connection from the config file - then the package uses what the connection was set to in development. It still will not use what we enter in SQL Jobs.
Furthermore, when we run the package we lose the values that we put in the DataSource tab!!!!
My work around has been to change the SQL Job type from an INtegration services package to a straight command line - this works.
The question is - can you set a package's connection strings from SQL Jobs using the SSIS Job Type ???
Thanks!!!
View 3 Replies
ADVERTISEMENT
Oct 9, 2007
I want to see if anyone in this community has come across this and has found a solution.
we have 3 different SQL Servers because we are still porting over SQL 2k databases 2k5. We have multiple databases of course. We would like to create some kind of template that would create the connection manager based off of the information in our XML configuration file. We are thinking we would have 2 files for this. One would house the actual server information but omit the database name and username/password. The second will be a list of all the databases with their usernames/passwords for each one.
If we put all of these in the configuration files and do not have a connection for each one, SSIS will throw the error stating it is missing connection managers for those items. We would like to see about maybe specifying the database name and have the connection manager dynamically pull the database specific information into the package. This would also need to be able to handle more then 1 database should there be the need.
I am new to SSIS. It seems pretty nice and extensible but my learning curve on it is horrible as I never programmed DTS packages before.
I hope I am making sense here. Thanks for any help offered!
- Taco
View 5 Replies
View Related
Aug 23, 2007
Hey there,
I know that many articles have been written describing configurations for packages but I have yet to have found one that describes if it is possible to use SQL Server configuration type for a package that is to be tested on DEV, then UAT, then PROD boxes.
I would like to know if there's a way to store values in a config table in a database on DEV, UAT and PROD but never have to change anything in the package.
I mean, I wonder if I can pass a parameter that defines the server to go get the configurations from.
The 3 servers will contain a database with a config table named the same on each server but have different configuration values to point them to the proper sources and destinations depending on which server the configuration database resides.
Thank you,
Robin
View 13 Replies
View Related
Dec 13, 2007
I have a problem where in I am trying to set up the package in a new environment.
I just need to change the server to which the data flow task will be populating.
I know we have xml configuration file. Is there any way i can read the files from .NET code and change the server name.
Thanks
Sai
View 4 Replies
View Related
Feb 6, 2006
http://img96.imageshack.us/my.php?image=untitled5ia1.jpg
how come my SQL 2005 surface area configuration don't have the configuration for SIS and other settings? seems to be missing alot of settings...it only say SQL 2005 Express when I m using SQL 2005 enterprise....
View 2 Replies
View Related
Apr 10, 2007
Hello, I have a SSIS package that is making one database connection (dbMAIN). I am using the XML File Configuration to specify dbMAIN's properties (server, database, password, etc).
The problem is that the File Configuration contains entries for multiple databases (dbMAIN, dbTEST, dbSTAGING, etc)
When the SSIS is run through dtexec.exe, I get this error:
Error: 2007-04-10 16:52:23.39 Code: 0xC001000E Source: TEST Description: The connection "DDMAIN" is not found. This error is thrown by Connections collection when the specific connection element is not found.End Error
I do not want it to give me an error. The XML File must house all our database connections. What can I do?
`Le
View 5 Replies
View Related
Jun 20, 2007
I have a package that executes several other packages. I have an XML packageconfiguration file to set the servername for the parent package, do I need to just add that packageconfiguration to the parent package and the servername in the XML file will be used until all the packages executed from the parent package are executed or do I need to add that configuration file to each lower level package?
Thanks for any help.
View 5 Replies
View Related
Jan 21, 2000
Hi Sql Pro,
Can u help me answer these 4 questions....
Can u schedule system/user databases backup when they are currently being used..
Does SQL Agent automatically start when u start SQL Server , if not why..?
Yesterday I setup a new server and most of the backup scheduled for midnight failed ...what maybe the reason...?I had set up all jobs as previously...?
What does the red 'X' against each job in the job scheduler indicate..?
Is there anyway u could start SQL Agent automatically ?????
Regards,
Bindu....
View 2 Replies
View Related
Mar 19, 2007
I have a package that uses configurations to override package settings based on what environment the package runs in. The package's configuration entries begins with an initial XML config entry that overrides the package's connection manager to a SQL database that holds the remaining configs in a table. Subsequent config entries then fetch their settings from the table. This package is run from a SQL job.
This all works fine in dev. When I moved everything into prod the packages are not getting configured and are using their values stored in the DTSX files. I've triple checked the XML config file, the tables with the configs, and the packages. There are no error messages. I've added some debuging steps to the package to verify that the configs in the table are not getting into the package.
I've also tried manually changing the configs in the table where the package is set to look if the initial XML config fails to adjust the config database location. The package still fails to see any configs from the table.
What could be different between dev and prod that would produce this situation? Both dev and prod have identical copies of the package and the job and are currently pointed to the same configurations database.
By the way, the other connections in the package work for both source selects and destination inserts. Only the configurations are failing, and again there is no error message.
View 6 Replies
View Related
May 6, 2008
I am using package configurations to hold an email address. I can happily change the email adress when teh config is in an XML file, but when I choose SQL Server to store the package configurations I can change the email address but the changes are not picked up despite coming out of dev studio and back in again - it picks up the default set on the variables tab.
It simply refuses to pick up the email address from the SQL table, but happily creates the dbo.[SSIS Configurations] table with correct entries in the wizard 1st time round.
Any ideas what I am doing wrong ?
View 10 Replies
View Related
Mar 27, 2001
Hi,
Schedule backup job which usually completes in 1 to 2 minutes, it's been running for over three hours. Meanwhile transact log backup job executed and it's hanging also.
I stopped the jobs, which now shows last run status 'cancelled'. But the spid still exeists in 'current activity' pane with status 'runnable'.
No locks or blocks!
Is there anyway I can get rid of this spids so that I can start backup job again?
It's very urgent..
THanks
View 4 Replies
View Related
Jan 17, 2001
Hello,
Does anyone has a script or knows how to find out whether the schedule job completed or not?
If I schedule the job to backup all databases on server and e-mail me when job completes.
But one time the job got stuck and somehow never completed. Is there a way I can schedule the job to see whether the other job completed or not?
Thanks for the Help
Rea
View 2 Replies
View Related
Sep 18, 2007
Hello everyone,
I am working on a SSIS project and I am facing an issue for getting the configuration settings of the package, once it is deployed and executed from SQL Server agent.
The package uses two configuration types: (listed bellow in the order they are appeared in the configuration editor)
Config1 - Xml configuration file - for storing the database connection string.
Config2 - SQL Server - for storing some user defined variables. It uses the same database as specified in Config1.
Everything works fine and the package uses the database configuration values as defined in Config2, if I execute it from Visual Studio,
However, the package doesn€™t get the configuration settings from the database when I try to execute it as a SQL Agent job.
There aren€™t any errors and the package executes all tasks successfully, using the connection object Config1 (the same we use to get the config parameters from the database) and the default values of the user defined variables.
It works ok, if I change Config2 to be of type XML configuration file.
There could be two problems:
1. SQL server agent doesn€™t read the configuration from the database and I am not quite sure how to set this. In Agent/ Job step properties screen/ Configurations tab I can only browse for a config file. I can also use the command window and /CONFIGFILE option to specify xml file, but how to use it in a case of a database configuration? Is there a /CONFIGDATABSE option or /CONFIGFILE works with database connection as well. I tried with /CONFIGFILE and database connection, but it doesn€™t seem to work.
2. SQL server agent doesn€™t get the configurations in the specified order. In my case,
it could try to read Config2 first, but at that moment it doesn€™t have the database connection from Config1 and it fails. Again, I am not sure how to set the sequence.
Thanks in advance for your comments.IT
View 12 Replies
View Related
Feb 22, 2008
I tried to follow this link last night (http://curionorg.blogspot.com/) but when i try to configure my package configuration to use sqlserver i recieved the following error message:
The Table "[dbo].[ssisencryptedconfiguration]" cannot be used as a source for SQL Server configurations. The column "ConfiguredVaue" does not have the expected data type.
consult books online for the schema requirements
I followed the blog line by line. i have closed down my project and created a new test package, new project, still the same error. Its there a property somewhere that needs to be configured to allow package configuration to use encryption with sqlserver? I'm running sql 2005 w/sp2. Its there a hotfix that i'm missing. i have not been able to google an answer.
I have been able to successfully use sqlserver as my package configuration. I wanted to see if i could use the encryption code posted on the blog above. i have seen folks reference it or point other folks to it to use for encypting sqlserver package configurations, i just wondered if they have had the same problem.
thanks
View 5 Replies
View Related
Jul 27, 2001
When I change the SA password on my server the current Scheduled SQL Jobs no longer work. If I run DTS packages by themselves and not from the Scheduled job window they work fine. I am using the sa as the Owner of the jobs and my SQL Agents services use a Domain Account. If I rebuild the jobs after the sa password is change they work fine. However, I don't want to rebuild 100 jobs every time I change my SA password.How can I fix or get around this problem without rebuilding my jobs?
View 5 Replies
View Related
Dec 29, 2001
Hi,
I have SQLServer 6.5 SP5a update running on Windows NT 4.0 SP6
with 4 gig RAM and 4 processor.
Suddenly the SQL 6.5 jobs running on the production server started running very very slow. A job that suppose to run in 30 minutes are running like 2 hours and completing successfully.
(I suspect the after the Norton Anti virus automatic live update may be the reason but not the Second Vulnerability as mentioned by Microsoft Bulletin last week)
I check the SQLServer, ran the performance monitor, checked pagefiles, disk space, databases,memory, tempdb. Everything seems to be normal.
I rebooted the server, checked any other process making that slow. But no use.
Please help me out with this issue as this is a production and the CRM applications from the clients uses the database server.
Thanks in advance,
Anu
View 1 Replies
View Related
Jan 26, 2006
I have two SSIS projects each with different packages. I have setup the packages with configurations stored in a SQL Server table in MSDB. When I create the configuration on the second project it overwrites all of the first projects configurations. Is there a way to to get two different project configurations stored in the same SQL Server table? Any help would be greatly appreciated. Thanks!
View 6 Replies
View Related
Nov 3, 1999
Hi,
I have a very peculiar problem. I have few CommandExec jobs on SQL Server 7.0 which has been scheduled to execute at a specific time. The jobs are executing properly but, the problem is they stop after the completion. i.e after finishing the jobs they still flash a message "Executing the job" they don't flash the message "Not Running" this is happening only to commandExec jobs, I have also few TSQL jobs which are working properly. I tried even giving the duration (start and stop time) but no use. Has anyone encountered this problem? If you have a solution PLS pass it on to me. I am in a very desparate situation.
Thanks in advance.
Robert
View 1 Replies
View Related
Mar 22, 2002
I am not able to run more than 8 jobs in SQL Server using SQL Agent JOB.
Any ideas and suggestions.
Thanks in advance.
View 3 Replies
View Related
May 8, 2008
I'm learning SSIS, and just started to use SSIS Package Configurations. I want to be able to switch between a dev and prod instance of our database.
I did not specify the password in the Configuration file (XML), figuring it would get it from the package itself. (That will be the same between dev and prod). But once I set up to use the Configuration, I started to get a "Login failed..." message. I added the password to the configuration, and it's the same. I quit using the configuration file at all, and then it works again.
This may be related, but when I show the properties on my connection, it shows stars for the password. When I go to the editor, the password field is blank, and if I test the connection, it fails. I type in the password, and then the connection works. I have the "Save my password" checked, but every time I go back, the password is blank. In fact, if I type in the password for the connection in the editor, and then go to the "All" page, the password is blank. It may be a red herring, but it sure looks like it's not really storing the password, and thus the Configuration file can't connect when it tries to get it. I can type in the password, test the connection (it works), close the editor dialog, open the editor dialog, test the connection again, and since the password is now blank, the connection fails.
What do I have to do to make that password actually stick!?
Without the Configuration file, when I save the package to SQLServer, it will run as a job, in spite of the password appearing to not stick. With the configuration file, it's not even running while still in Studio.
Here are at least some of the version information, which may or may not be useful.
Microsoft Visual Studio 2005
Version 8.0.50727.42
Microsoft .NET Framework
Version 2.0.50727
Installed Edition: Professional
Microsoft SQL Server Analysis Services Designer
Version 9.00.3042.00
Microsoft SQL Server Integration Services Designer
Version 9.00.3042.00
Microsoft SQL Server Reporting Services Designers
Version 9.00.3042.00
SQL Prompt 3.5
Thank you for any help you can provide.
-thursday's geek
View 12 Replies
View Related
Jan 24, 2007
Hi:
After moving my deployment folder to the Target Server, I run the Installation Wizard. As I move next, I am missing the window which is supposed to allow me to set package config values as stated in MSDN:
"If the package includes configurations, you can edit updatable configurations by updating values in the Value list on the Configure Packages page."
Source: http://msdn2.microsoft.com/en-us/library/ms141802.aspx
Does anyone know why I am not seeing it? In my deployment bundle which I have moved over has currently 3 files:
1) SSIS Deployment Manifest
2) SSIS Package
3) SSIS Config File
Again, I double click on SSIS Deployment Manifest, and it starts fine. I go thru the steps for File System Deployment, and then it prompts for installation folder path. After that, it takes me directly to validation. Why is it not showing me the Configure Packages Page as described in the MSDN Documentation. Please advise. Thanks.
View 5 Replies
View Related
Oct 20, 2015
I want to store multiple config files into single table I am unable to do it.
View 8 Replies
View Related
Nov 5, 2007
what is the equiv to dtsrunui to create the operating system (CmdExec)....
anyone have a good site suggestions for ssis outside of bol
View 2 Replies
View Related
Feb 8, 2008
Hi
I have a strange scheduling problem.
I have a job, i test it through BIDS - Works
I test it through SSMS - works
I run the job - Works
I schedule for a run time job - Works
I schedule for a recurring job - Works
However (here is the really annoying part) it fails to run at the night run (11.20PM)
there are 6 other packages that run fine after it , 11.30 , 1AM .. 4 AM etc ...
So
last night I changed the package to run at a later time, and it worked, but the other package that
ran 2nd (which now ran 1st) failed !!
its almost as if the 1st package has to fail !!!!!
When i look at the history and detailed log all it says is "The step Failed"
anyway , I can set up a workaround by starting a dummy job that is supposed to fail..
FYI the jobs are run under administrator and they are protected by a password (encryptSensitiveWithpassword) .
View 3 Replies
View Related
Jan 31, 2008
I have a brief question.
With a DTS scheduled job if I needed to make a modification, I just changed the DTS and saved it, and the job would automatically
Run the latest DTS (so long as the name was the same)
When I migrate a package to SSMS and schedule it , if I need to modify the package, do I need to modify it through BIDS (visual studio), then re-import it to SSMS and then reschedule it ?
Or is there a quicker way of modifying it ?
Thanks
View 2 Replies
View Related
Jul 10, 2015
I have just started to use Integration Services Catalog with SQL Server Agent. After I deploy a new version of the project the any Server Agent job that uses any of dstx still uses the old one. How do I fix this?
View 1 Replies
View Related
Feb 21, 2007
On my laptop I've got SQL2005 developper edition SP1 with 3 SSIS-jobs scheduled through SQL-agent.
These 3 SSIS-jobs are in fact maintenance plans which are also used on our production SQLServers.
These take backups (full, transactional), Cleanup old backups, reorganize indexes, update stats ...
One of these jobs runs every hour to take transaction logbackups. After installing SP2 this started failing.
When I opened the sources of that job in visual studio It seemed like the unit of thime was changed for cleanup jobs fe cleanup bak-files after 4 days changed into after 4 hours. The backup task for transactional backups which had the property to do that for all databases whas changed into specific databases which no database selected.
Even when I changed that into All databases and saved it, when I opened that backup task again, this was changed back into specific databases with no database selected.
I uninstalled SQL2005 and reinstalled it, including SP1 and everything works well again.
Does anyone know how to solve this.
View 6 Replies
View Related
Dec 2, 2007
I am hoping someone can help me with a problem I am having with SSIS. I am attempting to move certain sql agent jobs from our older sql 2000 server to our new sql 2005 server and I am receiving the error [Transfer Jobs Task] Error: Execution failed with the following error: "The specified '@server' is invalid (valid values are returned by sp_helpserver).".
Does my server name need to be the same if I am using SSIS to transfer jobs? Is there a way to update the server name during the execution process?
This seems like it should be a relatively easy task but has not been so far.
Any help is appreciated.
View 1 Replies
View Related
Jun 26, 2007
I'm having an issue in SQL Server 2005 with jobs that execute SSIS packages. The jobs run fine for a week or so, then I'll come to find that four or five (of the ten or so jobs) are hung in "executing" status. They seem to hang indefinitely (as some have been "executing" for hours with no end. The schedules of the hung jobs are all different, varying from every 10 minutes to nightly. The packages perform completely diffent tasks, as well. I can't seem to find any common thread with the jobs that get hung, other than they are all executing SSIS packages.
I've tried manually stopping the jobs and restarting the agent and SQL Server but the jobs hang again on there next scheduled run. The only thing that fixes the issue is rebooting the box, and then the jobs hang again in a week or so. Could some sort of memory leak be consuming resources throughout the week and be causing the jobs to eventually hang? I just rebooted the box and the sqlagent90.exe process is currently using about 7mb of memory. I'll keep an eye on it. Any other suggestions?
I've thought of creating another job that stops jobs that are hung, but what's to say that this job won't get hung as well? Plus this seems like a band-aid fix...
I don't recall having these problems until installing SQL Server 2005 SP2. Could this be related? I've searched like crazy and still can't find a resolution to this. It's becoming a big PITA...
Anyway, any suggestions would be very much appreciated!
View 6 Replies
View Related
Sep 10, 2007
I would like to create an SSIS package in 2005 and run it in 2000. Is there anyway to do this? Or does SQL Server 2000 have a precursor to SSIS? I am trying to create a job to automatically catch and kill orphaned processes.
-Kyle
View 1 Replies
View Related
Aug 5, 2015
I have created simple package loading data from source to destination.in BIDS working fine, but when i created job through sql server agent job I am getting below error.
Error:- The Job was invoked by User . The last step to run was step SQL AGENT JOB.
View 6 Replies
View Related
Mar 12, 2007
Hello All,
My database application has certain stored procedures which are scheduled to run at certain predefined interval (say once everyday). Now to implement this logic I have two options with me, first being to use the EXECUTE SQL TASK of the SSIS package and schedule it using the windows scheduler and the other is to use the SQL Server Agent Jobs and schedule it there itself. Now the current implementation is using the SSIS packages and I even know that the second approach of using the SQL Server Agents Job is better.
The only thing I want to know is whether it makes sense to invest time in converting my SSIS packages (20 in all) to SQL Server Agent jobs or not. Can somebody briefly explain or give some pointers regarding the performance benefits of Agent Jobs over the SSIS packages.
Thanks in Advance
Mitesh
View 5 Replies
View Related
Jul 14, 2006
Just an FYI for those scheduling SSIS packages on 64bit Itaniums.
This came to light when using a 32 bit OLEDB driver on a 64bit Itanium.
When manually executing the package on the server through SQL Management
Studio, we got the expected results. However, when we scheduled the
package as a job, it failed every time. The error was:
"The AcquireConnection method call to the connection manager 'ConnectionName' failed with error code 0xC0202009€?.
We tried everything to fix this, but nothing worked. Finally we found
that when manually running the package, SQL Management Studio was calling the
32bit version of dtexec.exe, while the Agent calls the 64bit version of
dtexec.exe. The fix is to not use the "SQL Server Integration
Services Package" type in the job step, but use "Operating system
(CmdExec)" type. Then in the command box, call the 32bit (x86)
version of dtexec.exe.
Example:
C:Program Files (x86)Microsoft SQL Server90DTSBinnDTExec.exe /DTS
"File SystemSSIS Packages[PackageName]" /SERVER [SQLSERVERNAME]
/DECRYPT [password] /MAXCONCURRENT " -1 " /CHECKPOINTING OFF
/REPORTING V
View 1 Replies
View Related
