How To Use The Deply Menu From Within The Project In Solution Explorer
Jan 21, 2008
I'm stuggling to find information on how to use the Deploy menu within a project in solution explorer. I would like to understand how to setup modify and delete the attributes that affect the actions of the Deploy menu. How to set different settings so that I can deploy to a test server ad then later change it so that I can deploy to a production server.
I am a Visual Studio .net developer and understand Solutions and Projects in VS.net. Nevertheless, it appears that the paradigm of using Solutions Explorer in SQL Server is not exactly the same. That is, in Visual Studio you can't get anything done without creating a solution first. In SQL Server, it is entirely possible to get a lot done without a solution and the ability to create and make use of a solution seems almost an after thought or an add-on. I am particularly interested in using a solution in SQL Server to allow me to make use of SourceSafe. In the past, we jumped through all kinds of hoops to keep a running trail of changes we had made to (for example) stored procedures. It appears now that this can be managed more efficiently with the use of a Solution and SourceSafe and saving scripts or .sql files. I guess it is not possible to save a pristine copy of a stored procedure directly in SourceSafe, but you can save the code that makes up the stored procedure as a .SQL file which I suppose is about as good. Anyway, what I would like to know is whether there is a good white paper (or chapter in a book) on the philosophy behind Solutions and projects in SQL Server and how MS intends us to use them; perhaps something other than the cold facts from the documentation. I would appreciate something more that gives me the big picture on just how MS sees them being used in SQL Server so I can get the most out of them. I have the feeling that if I "get the vision", they are meant to be an integral part of SQL Server now and in the future. Woody
Good afternoon, This is a simple question....how can I order packages by name in solution explorer ? I have a solution with more or less 50 packages and it's very ime consuming to find a package ! ehehe
When trying to create a data source in Solution Explorer the Provider is greyed out and only allows me to create a connection to a SQL server database although I can connect to an oracle database in Server Explorer
Hi.. Isn´t it possible to create sub folders in the solution explorer?? I have it hard time to create a decent structure inside the SSIS Package folder, since I have like 30 packages in my project. Is it just me being silly or cannot this be done?
Can the items, i.e. reports within the SSRS Report Designer Solution Explorer be arranged in a custom manner instead of being sorted alphabetically only?
When you create a Reporting Services project it by default creates two folders: Shared Data Sources & Reports. When I right click on the Reports folder in solution explorer in Visual Studio 2005 there is no option to add subfolders, I am simply left with handful of options adding report files. Is there a way to add subfolders to the Reports folder? I am going to be migrating over 40-50+ reports and it would be helpful to organize them into their own folders.
I've submitted a bug report for this, but I also want to be sure it's not my own installation.
In the solution explorer, when I drag a package (usually accidentally) to another spot in the list, it disappears from the list. If I try to re-add the package, it thinks the original already exists, and names the second one with a "(1)" suffix. I can work around this by moving the original package out of the primary package folder and then re-adding it through solution explorer, but that's a touch cumbersome.
I don't really have a question here other than perhaps validation of the issue. Thanks.
Here's the bug report if others experience the same issue: https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=258908
Yesterday, SQL Server 2005 SP2 was installed on our DEV Server (Windows 2003 SP1 x86) and now I cannot right-click a package in the Solutions Explorer window in BIDS and Execute Package. When I do, I get the following error
===================================
Object reference not set to an instance of an object. (Microsoft Visual Studio)
------------------------------ Program Location:
at Microsoft.DataTransformationServices.Project.DtsPackagesFolderProjectFeature.ExecuteTaskOrPackage(ProjectItem prjItem, String taskPath)
I know I could do this yesterday morning pre SP2. I've attempted this with a couple of different packages and solutions, so it is probably not a corrupt package (unless now they are all corrupt). I can execute in debug mode if I open the package first and then hit Start Debugging. However this is not always an optimal solution because I sometimes have many connected packages and sometimes what gets executed is not what is expected.
In SQL Management Studio Express, is there any wany to save the "solution" consisting of the set of queries that I have open at a point in time?
I generally have 10 views I switch back and forth between to monitor a bunch of data load processes, and it would be helpful to be able to return to the same setup next time I login.
I have a solution with a couple of ssis projects in it. Everytime I open the solution, Visual Studio creates an extra .database file for the project's existing xxx.database file. The solution is under VSS control and VS2005 checks out the project and shows the file as a newly added file.
What causes this and how can I prevent this from occurring?
There are 2 of us working on the solution and the other fellow does not see this behavior.
The files do not show up in the VS2005 solution explorer. If they are user specific as I suspect (impersonation info?), then they should not be added to the .dtproj project file.
If there's an SQL 2005 admin around, I'd appreciate an interpretation on the below error. I'm trying to deploy an SSIS package to a shared SQL 2005 host. They claim they allow installations of such packages, but it appears to me they do not have permissions setup correctly.
- - - - - - - - - - - - - - - - - - - - Additional information - The SavetoSQLServer method has encountered OLE DB error code 0x80040E09 (The EXECUTE permission was denied on the object sp_dts_putpackage... - - - - - - - - - - - - - - - - - - - -
Can someone advise instructions on what I can tell them to change on their end? .. or my end?
we have automated build on every night. In our solution is SSIS project, where each package is encrypted per password. We call build process per command line like this..
C:ProgrammeMicrosoft Visual Studio 8Common7IDEdevenv.exe (c:DevelopmentX3\X3.sln /build Release)' in 'c:DevelopmentProjectsDailyBuild
Through build process we get a error:
External Program Failed: C:ProgrammeMicrosoft Visual Studio 8Common7IDEdevenv.exe (return code was 1):
We think a reason is, that on build of SSIS project must be entered a password. You can wonder for what we need that SSIS packages are part of our build. We hope that on build process is also created Deployment Utility, if so set in dtproject.user. Is it so? Is there any way to create Deployment utility on automated build process? Can be a password provided pre command line?
For some reason in a Team Foundation Team Project that has multiple project types (SSRS, SSIS, WebSite, C# Business DLL...), the SSIS project makes itself the startup project to the team project. If I explicitly set another project as the startup project to the team project and then select an SSIS package in the SSIS project in the team project, the SSIS project becomes the startup project automatically.
I just realized recently that a database "XYZ" in the Object Explorer of my SQL Server Management Studio Express (SSMSE) is put in the Database Explorer of my VB 2005 Express for processing a Stored Procedure in executing the SELECT statements (not by using Input and/or Output Parameters) during the ADO.NET 2.0-VB 2005 Express programming, then the content of the database "XYZ" is not in the SSMSE. How can I return the database "XYZ" from the DataBase Explorer of VB 2005 Express back to the Object Explorer of SQL Server Management Studio Express (SSMSE) safely? Please help and advise.
I have been working on some SSIS packages for a while now and today while i was working i was trying to create a new connection and in the process there was an error and it said the BIDS has to be closed and i closed it but later when i open BIDS and try to open my project(.sln) from the file menu to work on the half done package it pops up an error which shows the path to my project location on the first line and next statement on the pop up error box says:
"Make Sure the application for the project type (.dtproj) is installed."
I tried to check some forums in which some suggested to try installing SP1 which i tried but ..i dont know why but the SP1 fails to install (i dont know if its causing problem becoz i already installed SP2 as i had some other problem before for which the cure was to install SP2).
Did anyone here face such a problem before ?
I'd really appreciate if the experts here can tell a cure for this problem.
I have a Visual Studio 2005 solution which contains a Sql Server Integration Services (SSIS) project.
In this solution I have explicitly set a Web application project as startup project, but whenever I edit a DTS package within the SSIS project, VS automatically sets the SSIS project as startup project and the package I edit as startup object.
Needless to say, this may cause some really unwanted incidents when running the solution - thinking that you're about to run the Web application project (that was explicitly set as startup project), but instead, you run the edited package in the SSIS project.
Is there any way to avoid having the SSIS project automatically setting itself as startup project, any workaround here at all? :)
VB.NET 2005 Express and SQL Server 2005 Express - NOT saving updates to DB - SOLUTION!
-----------------------------------
The following article is bogus and confusing:
How to: Manage Local Data Files - Setting 'Copy to Output Directory' to 'Do not copy' http://msdn2.microsoft.com/en-us/library/ms246989.aspx
You must manually copy the database file to the output directory AFTER setting 'Copy to Output Directory' to 'Do not copy'.
Do not copy
The file is never copied or overwritten by the project system. Because your application creates a dynamic connection string that points to the database file in the output directory, this setting only works for local database files when you manually copy the file yourself.
You must manually copy the database file to the output directory AFTER setting 'Copy to Output Directory' to 'Do not copy'.
-----------------------------------
The above article is bogus and confusing.
This is rediculous!
This is the most vague and convoluted bunch of nonsince I've ever come accross!
Getting caught out on this issue for the 10th time! And not being able to find an exact step-by-step solution.
--------------------------
I've tried it and it doesn't work for me.
Please don't try what the article eludes to as I'm still sorting out exactly what is supposed to be happening.
If you have a step-by-step procedure that can be reproduced this properly please PM me.
I would like to test its validity then update this exact post as a solution rather than just another dicussion thread.
Many thanks.
This is the exact procedure I have come up with:
NOTE 1: DO NOT allow VB.net to copy the database into its folders/directorys.
NOTE 2: DO NOT hand copy the database to a folder/directory in your project.
Yes, I know its hard not to do it because you want your project nice and tidy. I just simply could NOT get it to work. You should NOT have myData.mdf listed in the Solution Explorer. Ever.
Create a folder for your data following NOTE 2.
Copy your data to that folder. * mine was C:mydatamyData.mdf
Create a NEW project.
Remove any Data Connections. ( no matter what)
Save it.
Data | View Data Sources
Add New Data Source
select NEW CONNECTION ( No Matter what, do it!
Select the database. * again mine was C:mydatamyData.mdf
Answer NO to the question: Would you like to copy the file to your project and modify the connection? - NO ( no matter what - ANSWER NO ! - Absolutely NO ) Then select the tables you want in the DataSet. and Finish.
To Test ----------
From the Solution Explorer | click the table name drop down arrow | select details Now Drag the table name onto the form.
The form is then populated with a Navigation control and matching Labels with corresponding Textboxes for each field in the table.
Save it.
1) Run the app.
Add one database record to the database by pressing the Add(+) icon
Just add some quick junk data that you don't mind getting lost if it doesn't save.
YOU MUST CLICK THE SAVE ICON to save the data you just entered.
Now exit the application.
2) Run the app again.
And verify there is one record already there.
Now add a second database record to the database by pressing the Add (+) icon.
NOW add some quick junk data that you WILL intentionally loose.
*** DO NOT *** press the save icon.
Just Exit the app.
3) Again, Run the app.
Verify that the first record is still there.
Verify that the Second record is NOT there. Its NOT there because you didn't save the data before exiting the app.
Proving that YOU MUST CLICK THE SAVE ICON to save the data you just entered.
Also proving you must add your own code to catch the changes and ask the user to save the data before exitiing or moving to another record.
As a side note, since vb.net uses detached datasets, (a copy/snapshot of the dataset in memory and NOT directly linked to the database) the dataset will reflect all changes made when moving around the detached datasets. YOU MUT REMEMBER TO SUBMIT YOUR CHANGES TO THE DATABASE TO SAVE THEM. Otherwise, they will simply be discarded without notice.
Whewh!
I hope this saves me some time the next time I want to start a new database project.
Oh, and uh, for anyone else reading this post.
Thanks, Barry G. Sumpter
Currently working with: Visual Basic 2005 Express SQL Server 2005 Express
Developing Windows Forms with 101 Samples for Visual Basic 2005 using the DataGridView thru code and every development wizard I can find within vb.net unless otherwise individually stated within a thread.
in order to maintain a deployed project into an Integration Services Catalog I'd like to know if it is possible to import it into a new project inside SSDT.
I want to update value of a custom field for a perticular project in Project Server 2007 using PSI.
I have created 5 enterprise custom fields(A,B,C,D,E) through PWA/Server Settings.
I want to search all Projects on Server. If any project is having value for custom field A then I want to update rest of the custom fields(B,C,D,E) for that perticular project.
I have a very small project written in VB.Net 2005 using the SQL Server 2005 SSiS DTSx package.
I took a SQL Server 2000 dts package and using the SQL Server 3005 legacy tools migrated it so I could still use the package withing SQL 2005 until I can build one using BI/SSIS.
Anyway,I added the reference Microsoft.SqlServer.ManagedDTS so I could then use the Microsoft.SqlServer.Dts.Runtime so I can execute the commands:
Dim oApp As New Application Dim oPkg As New Package oPkg = oApp.LoadPackage(g_DTSx_Directory & "AOC copy Generic1 CSV to AOC_verify_file_1.dtsx", Nothing) Dim oResults As DTSExecResult oResults = oPkg.Execute
Ok. That works fine. Executes without a hitch. So now I try and create a setup project for this and I use the setup wizard.
During the creation of the setup project I get a message that states: The following files may have dependencies that cannot be determined automatically. Please confirm that all dependencies have been added to the project. C:windowssystem32msxml6.dll
OK. The dll is part of the reference I mentioned above and I have no idea what other dependencies it may have.
How do I find this out?
Has anyone else created a project like this and experenced the same?
I am on a clean build running WinXP Pro with SP2 - VS2005 with SP1 and the SQL Server 2005 tools.
I've got an SSIS solution file with project deployment model in VS 2013 and would like to deploy that to SSISDB on different environments.All these days I followed the regular way to create a project in SSISDB and deploy it to that. Now want to find out if i can automate this process and so got some questionsÂ
1. Can we automate the process of creating a project on SSISDB based on our SSIS project name? This will be like when we do a deployment it should check if the project exists or not on SSISDB based on our SSIS project name, if the project exists we just deploy the packages in the project and if the project does not exists in SSISDB it will create that project and deploy the packages.
2. Can we also automate the process of creating environments? In traditional way we manually create the environment variables under environment tab of SSISDB, but can we make that also as part of deployment? Like when we are releasing to Dev server we look if that particular Dev variable exists on that server, if it exists we just update the existing stuff and if it does not exists we just create it.
I have visual studio 2005 and sql server 2005 with integration service installed on my machine. Couple of days ago, I installed visual studio 2008 professional. When I go to create SSIS project I dont see it in visual studio 2008. What do I have to do to make it appear in visual studio 2008 so that I can create SSIS projects.
I fail to use project professional 2003 to access to the project server 2003 using MSDE 2000 in local area network, following message was shown,
Connection failed:
SQLState: '01000' SQL Server Error 1326 [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()) Connection failed: SQLState '08001' SQL Server Error: 17 [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied.
I have seen these pages with similiar cases but can't help.
Do I need to re-create a new package from scratch after doing what I did? It seems I've made what is probably a typical newbie mistake: I used COPY/PASTE to consolidate containers from two packages into a single new project/package.
Now my new package generates multiple duplicate errors (23 of each...) whenever I open it:
Warning loading LoadBillingData.dtsx: Process configuration failed to set the destination at the package path of "PackageData Flow Task to Load Profiles, Versions, and Transactions.EventHandlers[OnError].Variables[System::Propagate].Properties[Namespace]". This occurs when attempting to set the destination property or variable fails. Check the destination property or variable.
Error loading LoadBillingData.dtsx: Changing the name of a variable failed because it is a system variable. System variables are read-only.
What happened:
new guy (goes without saying...) creates:
01. PROJECT A 02. add PACKAGE A to PROJECT A 03. add some containers, figger out what the heck is going on, get containers working 04. create PROJECT B 05. create PACKAGE B 06. add containers, they work fine 07. whoops! Want to consolidate the packages. Unix guy naively expects Bill has made MS Visual Studio like all windows products (of which newbie is aware€¦): 08. create PROJECT C 09. create PACKAGE C 10. <ctrl a> PACKAGE A 11. <crtl c> PACKAGE A 12. <ctrl v> PACKAGE C 13. <ctrl a> PACKAGE B 14. <crtl c> PACKAGE B 15. <ctrl v> PACKAGE C 16. copy Flat File Connection Managers 17. copy Database Connection Manager 18. drag the arrows around, fix the flat file sources, renew the column maps, etc 19. whoops! the connections all look like a registry number! Fix the OLE DB Destinations, Execute SQL Task containers by selecting the DB Connection Manager copied from PROJECT A
20. successfully execute PROJECT C/PACKAGE C 21. save all 22. exit 23. start MS Visual Studio 24. Open Solution 25. ERRORS!!!
Hello, I've created a Report Model Project that can be used by Report Builder to generate ad-hoc reports. I'm trying to create a connection string in my Report Server Project that points to the Report Model Project data source view.
All I can do is create a regular datasource, which bypasses the metadata contained in the Data Source View.
Basically I want my Report Server Project and my Report Builder reports to leverage the same metadata. Is this possible? If so how do I get the connection string?