When adding a SSIS DTSX package solution to Sourcesafe the SSIS Package Configuration file (.DTSConfig) is not included. We are using sourcesafe version 6.0d and Visual Studio 2005 Team Edition for Developers.
Recently, my company's deveolpment machine crashed. We had to format the harddrive which meant we lost some of our databases. We managed to restore the databases, but we do not know in what state, i.e. which stored procedures were written between the restore point and the point the machine crashed. Tow questions related to this: 1. I was wondering if there is any product that is similar to soursesafe but appied to databases, so that this problem will not happen again. Does Enterprise manager do something like this? 2. I was also wondering if there was anyway to undo an sql command. e.g. my colleague recently ran a command to update a database, but forgot to write the where clause!! That data was recovered aswell, but it would be nice to have some sort of undo button. Thanks in advance. Jagdip
Hi, How is it possible to link the stored procedures in sql server to Source Safe? The idea is that if anyone goes to sql server and wants to change a stored procedure, he has to check out/in, etc... Just like the way it is done is Visual studio with Source safe. Thanks
I've ready many of the posts on this and other newsgroups in whichpeople describe working practices for source control of databasescripts. We are looking to implement something similar in my currentworkplace.We have agreed that developers should not modify objects such as viewsor stored procedures directly, they should check the script out of VSSfirst, modify it, run it, and then check it back in.The problem we are having is finding a quick, easy way to run all thescripts in VSS in the right order, to create a new database. If wedon't run them in the right order the sysdepends table will beincorrect.If anyone has any suggestions please let me know.Regards,Ross NeilsonSoftware DeveloperInteractive Products Ltd.
Hi All... Well, another old c++ programmer has found the Lord - I've just written my first stored procedure. And yes, as I've always heard, it's quite cool...
The thing I've never really cared for though is that they sit way out there in the database, far away from all the "other" code. I'm presently involved in an asp.net project and we use SourceSafe. I've seen some mention of VSS with SQL Server on this site and am quite pleased to see it! But for the sake of an old c++ programmer, what are the basics about getting things like stored procedures (and even the database schema for that matter) into sourcesafe? That is what's the easiest way to do it? ; )
For what it's worth, we're using .Net 2.0, Visual Studio 2005, SQL 2005 and VSS 6.0. Thanks for the tips! -- Curt
I've figured out how to store new SSIS projects in SourceSafe, but is there a way to configure an agent job to execute a package from SourceSafe, or do I have to maintain a copy outside? (Which doesn't seem to make sense...)
HiIs it possible to use Visual Source Safe with SQL Server inorder to keep track of all modifications done to stored procedures?What are the pros and cons ?Thanks, Eugene
In SQL Express SP2, when I select Tools > Options, there is a place where I am supposed to be able to specify the source control plug-in. I have SourceSafe 2005 installed on this machine, so I see these choices in the drop-down:
None
Microsoft Visual SourceSafe
Microsoft Visual SourceSafe (Internet)
The problem is that whenever I select one of the SourceSafe options, it goes back to "None".
I'm not even sure how the source control intergration works, but I figured I have to select the plug-in before doing anything else.
How can I select the SourceSafe plug-in under SQL Express SP2?
Imagine opening SQL Server Management Studio (SSMS), drilling into adatabase, and seeing all objects with little lock symbols in front ofthem. That would be true SS integration.Maybe next version?I know about creating a project in SSMS and managing connections,queries, and misc there, but come on, that seems a far cry from what Ilong for.I searched for 3rd party tools and found SQLSourceSafe and Apex SQLTools. Does anyone have experience with those?-Tom.
I get errors when I check out an SSIS package from source control (both Source Safe and TFS) relating to the connection objects where I was not the original developer who checked it in. Is there a solution to this other than altering the connection loginpassword for every connection object in the package before deploying?
The develpment team where I work is using Visual Studio 2005, SQL Server 2005 and Team Fundation Server. We want to somehow track changes of the stored procedures. We could create a Solution/Project in the SQL Server Management Studio, add all stored procedures to it and add that Solution/Project to the SourceSafe but nothing will stop developers from directly altering stored procedures.
Any ideas on how to prevent developers from making changes to the stored procedures directly?
I've added an XML package configuration file to my SSIS package and it appears to be working fine.
The XML file is located in the same folder as the solution file.
I've recently added the entire solution to Visual Sourcesafe 2005, and I achieved this by doing the following:
1. Right-clicked on the Project name in the solution explorer and selected "Add to source Control". 2. When prompted, provided my Sourcesafe login credentials and clicked "OK" 3. Accepted the default VSS project name and clicked "OK" 4. Clicked "Yes" to allow VSS to create a new project
Problem: The XML configuration file hasn't be added to sourcesafe along with rest of the solution.
I'm able to add the file manually myself, but this doesn't seem right to me. Am I missing something? Should the config file show as part of the Solution in Visual Studio 2005?
I'm trying to easily change a value in 80 ssis configuration files from "localhost" to "myservername". I downloaded WinGrep to do this, but it's balking on some of the files, saying that they are binary files.
Does anyone know how to make the *.dtsconfig files NOT binary in SSIS?
Any suggestions GREATLY appreciated.
I won't go into the reason I have my servername in 80 places...
Hi, i'm new in this forum and in SSIS, so I apologize if mine is a stupid question and also for my english.
I have this problem: i have to develop an ETL package and i have to set the transformation between input and output columns using a configuration file, i.e. my client want to change the transformation simply modifying a config file( for example from UPPER to LOWER ).
I tried using dtsconfig and setting EvaluateAsExpression with value 1( true ) and Expression UPPER[Column 2] but i get an error saying that Column 2 is not a variable.
I have an SSIS package with a small number of connections for various databases, both SQL2K5 and AS2K5.
When I build the package the .dtsConfig file is produced but the contents for some of those connections are not accurate relative to the package itself. There are some old values retained in the .dtsConfig file.
Worse, when I deploy the package to another machine the installation should allow me to change these values to ones appropriate for the new server. While I am able to change them they are not retained and the old values crop back up making the package fail during execution.
Any idea where I can smack this thing to unstick these values?
Would specifics help? I can post the file(s) if need be.
Apologies if this has been posted before and feel free to point me to an existing thread if it has.
I currently have a dev, stage and live environment for a package
i have created a load.dtsconfig file that contains various bits such as connection strings, email to, from, etc which i created via the package configurations in the dev package. I then made a few changes via XML Notepad
I went to use the same config file on stage and decided to add a further property. I selected package configurations on stage and selected edit it the package configurations box, added the property and clicked finish. However it reset all the existing properties to the values that exist in the actual package so all the changes i made via XML notepad were overwritten.
Is there anyway you can get the Package configurations editor to retain the values from the .dtsconfig file rather than reading in the values from the package???
hi, all; i'd like to resolve this problem: We are Developing packages in Dev.Server; if we are Deploying our packages to Prod.Server; we need to modify the connection string and related properties of the connection manager. 1. How to modify the connection manager while deploying to production server? 2. can we create 2 dtsconfig file for a single package; is there any mechanism for instructing sequel server to use a particular dtsconfig file for our package.
i modified the config file in order to change the connection string. but its affecting only the config file not the package. while running the package its reffering the old connection string only.
hi i want to know what are the purposes of dtsconfig file for the package. once we deploy our package, if we want to modify the connection string for the new excel source or data source or destination, how to modify the connection details at client site, or in the server,
please help me to modify these connection details after or before deployment at server machine.
I am going thru the Integration Services Tutorial found in Books Online and I'm on Lesson 3. It has to do with creating a configuration file for the source file location. I followed the steps and now I need to open the .dtsConfig file and type in the folder location.
The exact direction says,
"
In Notepad or any other text editor, locate and open the SSISTutorial.dtsConfig configuration file that you created by using the Package Configuration Wizard in the previous task.
Change the value of the ConfiguredValue element to match the path of the New Sample Data folder that you created in the previous task. Do not surround the path in quotes.
Save the change, and then close the text editor. "
When I open the file, I see this. What am I supposed to do here?
it would be really useful. it looks like the .dtsconfig file needs to be maintained on each install independently. This makes maintenance a nightmare. it would be a lot nicer if the .dtsconfig files were more like templates rather than hard coded values to specific system resources.
after i attached the file in package configurations .
i was unable to see the db connection in connection managers.
i tried to attach the .dtsconfig file in (New OLEDB connection manager) but after clicking the test connection " Testconnection failed because of an error in intializing provider.The connectionString property is not intialized"
I was requested to build and move and existing SSIS package from the developers local PC to the Dev server. Both are running SQL 2K5, I built the following command file so SQL Agent can run the import job.
REM *** Run for FileImport set FileImportLoadData=C:SSISConfigDEVFileImportLoadData.dtsConfig "C:Program FilesMicrosoft SQL Server90DTSBinndtexec" /f "C:SSISConfigFileImportFileImportLoadData.dtsx"
All files are in the proper place but when the jobs runs the following message shows up in the history;
Message Executed as user: LIGHTHOUSE1SQLEXEC. ...system32>set FileImportLoadData=C:SSISConfigDEVFileImportLoadData.dtsConfig C:WINDOWSsystem32>"C:Program FilesMicrosoft SQL Server90DTSBinndtexec" /f "C:SSISConfigDEVFileImportLoadData.dtsx"Microsoft (R) SQL Server Execute Package Utility Version 9.00.3042.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 8:54:00 AM Warning: 2008-05-08 08:54:01.77 Code: 0x80012014 Source: FileImportLoadData Description: The configuration file "FileImportLoadData.dtsConfig" cannot be found. Check the directory and file name. End Warning Warning: 2008-05-08 08:54:01.77 Code: 0x80012059 Source: FileImportLoadData Description: Failed to load at least one of the configuration entries for the package. Check configurations entries and previous warnings to see descriptions of which configuration failed. End Warning Progress: 2008-05-08 08:54:01.82 Source... Process Exit Code 0. The step succeeded.
My questions is how do I fix this and is this really and error?
I use an XML configuration file for my SSIS package, and I have "Enable package configurations" checked. When I build the package, however, there is no dtsConfig file in the output (set to in) or the Deployment folder, and the config file is not included in the SSISDeploymentManifest file. There are no build errors or warnings.
This was working fine the last time I worked on this package (~9 months ago), but not now. I have since installed SP2, but can't confirm if the problem is related to a "fix" in SP2.
When I edit package configuration files inside of Visual Studio, it puts all the XML on a single line. Does anyone know how to automatically spread the information onto multiple lines, to make comparing file differentials easier.
Microsoft (R) SQL Server Execute Package Utility Version 9.00.3042.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 10:01:27 PM Warning: 2007-11-30 22:01:29.52 Code: 0x80012012 Source: Package Description: The configuration file name "C:DevelopmentdtsConfig.xml" is not valid. Check the configuration file name. End Warning ...
But then it goes on to read values from my Production config file. How can I stop the annoying warning about my Development config file-path (which doesn't exist on the Production machine)
I am migrating from local to Dev,QA and Prod. I created a .dtsconfig file containing database connection strings to Dev database. What is the "location" on the Dev server where this .dtsconfig file nees to be deployed to??
I have setup a package configuration and it ran fine; however, I would like to be able to use the script task to change content of the dtsConfig file. For example, I can get the newServerName using the SQL Task, then how can I assign the newServerName value to the DataSource in the package configuration file? Is this possible?
I've deployed my ssis pkg to the server and created a sql job to run this pkg. So far, everything is fine. Today, I got a request to change some variables inside the package which is part of the .dtsconfig. I want to edit the deployed .dtsConfig but it won't allow me and always complained that this file has been opened by another program. I am sure i've closed my ssis designer and other notpad, why can't I edit and save .dtsconfig file?
I have a job/step that call a Fileprocessor.dtsx package with 4 different config files. I need to make a enhancement to the job to call the same package using a new (parent) package with multiple iterations based on some business condition.
I am going to modify the job/step to call ParentFileprocessor now with same all 4 config files which in-turn have a call to run Fileprocessor.dtsx; my problem is, how do I pass all 4 config files for child call? Using which task?
I m not allowed to modify Fileproessor.dtsx (to be child pkg) SQL2012, MSDB package deployment model.
Hi all, I need one more help! we can select the dtsconfig file with the Environment variable(indirect configuration); but i need to select the configuration file at runtime; i've to load the package from the server and apply local configuration file to the package and run in a web server;
Requirements; 1. i have packages with its xml configurations for connection strings alone! 2. i deployed it on the server 3. Trying to execute the packages in a web page onclick event;
We have ASP.net WebPage; in On_Click Event, i have this code;
Application ap = new Application(); Package pk = ap.LoadFromSqlServer("\PROJECT", "itsssqldb", "pmo_package_user", "password", null); pk.ImportConfigurationFile(@"Packagesdev_staging.dtsConfig"); pk.Execute(); here PROJECT is the Package name; i'm loading the package from the Common Sequel Server 2005; and applying the configuration file to that package and trying to execute this; but its not using the config file what i mentioned; its returning failure!!
Can you please help me to resolve this issue!,
(The intention of doing this job is to select the configuration file( prod, dev) at runtime)