I am using TFS 2015 U3. Recently I have installed SQL Server Reporting Services Deployment (https://marketplace.visualstudio.com/items?itemName=tobania.SqlReportingServices#overview) in Market place.
Here is my question:
I think this is not an issue with extension but my question is how to handle the process.
Each time my release task runs it will deploy all RDL files in my project. Is there a way to only deploy new/ Changed RDL's(Is it possible to Deploy only new and modified reports (RDL files) using TFS Deployment?)
Thanks,
Satheesh
No, that's the expected behavior with the extension which deploy all RDL files in the project. It will relace all the previous files. Only deploy the new and modified reports (RDL files) is not supported.
However you can try deploy the files singly with powershell, below articles may helps:
PowerShell Commands for SQL Server Reporting Services
Related
We have an SSIS project in Visual Studio (2019 Community) that we deploy to our SQL server (2016) using project deployment. We have a couple of hundred packages and we most often deploy single packages at a time.
We had been doing most of our development in a single Azure Git master branch since these changes were separate from most of our other development. A few changes were done in a different development branch and then that single package was deployed from there. It should not have caused a problem because that single package was new and not being used in the master at all. However, when that single package was deployed it removed a couple of new packages from our live server that had been deployed from the master branch but had not been in the development branch when it was initially created.
I thought that a single package deployment only deployed that single package you selected or the few packages you selected if you chose a few of them. It seems like in addition to deploying that package it deleted packages that were on the live server but not in the dev branch that we deployed from.
We deploy from Visual Studio by right-clicking our package or packages and then choosing Deploy Package from the context menu. That process creates an .ispac file when we are deploying to our development SQL Server. That .ispac file is copied to the live server and then run directly on the live SQL server.
This should not be deploying all packages, correct? Just those highlighted? Does it remove missing packages if I only deploy a single package at a time but the packages in my project in VS and the project in the SSIS catalog do not match?
It depends!
For 2012 and 2014, the only option for deployment to the SSISDB was "Project" deployment. The entirety of the .ispac file is applied to the SSISDB - whether package1 had changed or not.
With 2016+, you have the ability to do Project or Incremental Package deployment. In the "Review" tab of the deployment wizard, in the Summary section you can see the command line indicates /ModelType:Package That is the indication it is deploying package(s) versus the whole project. See figure 5 of
https://www.sqlservercentral.com/articles/incremental-package-deployment-%E2%80%93-a-ssis-2016-feature
If you're deploying from the .ispac, then there should be a selector in the Select Source tab (not shown in referenced article) that allows you to do full or incremental deployment but the ModelType in the Review tab will identify which approach was selected. I suspect someone did a full/project deploy.
But, the nice thing about the SSISDB is that you can use SSMS to roll the project back to the previous state so no harm, no foul, no lost packages.
I'm trying to build a SSDT (SSIS) package from Visual Studio 2015 to my prod server that runs Sql Server 2016. I'm coming from a SSIS 2008 r2 environment that allowed me to build my packages and then copy the files over to the server and execute the *.SSISDeploymentManifest. Now when I hit Deploy in VS, it goes through the wizard, but it's asking for destination server information. I cannot connect directly to the prod server from VS or SSMS due to security. Is there a way to get VS to deploy(or build) the package and .ispac file locally and then I can manually more it to the appropriate server and then execute it?
So far, my only work around is to Build the package. However, I have found that it puts the .dtsx file in the obj\Development folder and the .ispac file in the bin\Development folder. Going back and forth to copy files for numerous packages is painful and I'm sure not the intended process.
We have assumed maintenance of a legacy 32bit application. I installed TFS 2008 to use in maintaining the project.
We will never use reporting or sharepoint. I cant create a project because of issues with SSRS.
(The Project Creation Wizard encountered a problem while creating reports on the SQL Server Reporting Services on OHSENSS801. The reason for the failure cannot be determined at this time. Because the operation failed, the wizard was not able to finish creating the SQL Server Reporting Services site. )
How can I disable reporting and sharepoint in TFS 2008?
Thank you.
Unlike TFS 2010 and above version, you have to install the SharePoint components for TF2008.
TFS2008 is a very old server version and out of support for a long time. You could use TFS2010 instead, the SharePoint is no longer a prerequisite when you install TFS2010. You can go for TFS2010 Basic Configuration which is the most compact TFS installation possible.
In Basic Configuration, SharePoint and Reporting Integration will not be possible. It will install and configure Source Control, Work Item tracking and Build Services only.
Highly recommend you to move to a newly versioned TFS server. If you insist on using TFS2008, you could try to troubleshoot the configuration of SQL Server Reporting Services. Details please refer this thread in MSDN: SQL Server Reporting Services is not configured correctly
About how to remove Sharepoint and Reporting Services from TFS, you could go through this question. However, afraid removing these components, you will still not able to create team project. After all, if it will work, there is no need to be a prerequisite for installing TFS2008.
Sometimes it is necessary to republish the CRM reports by going to C:\Program Files\Microsoft Dynamics CRM\Tools\ on the server and running PublishReports.exe (http://community.dynamics.com/crm/b/crmguyriddle/archive/2008/06/26/re-publish-crm-reports-in-srs.aspx).
Is there an CRM 2011 SDK method to do this from code (C#)? I want to do this from an application running on a remote machine.
There is no CRM SDK method to do what PublishReports.exe does. PublishReports.exe calls methods from the CRM setup DLLs (not part of the SDK and are not available to the CRM server code itself.)
In short, what PublishReports.exe does is exactly what the CRM Org Setup process does to get the reports to SQL RS - first, it creates the shared data sources and then it reads the report information from the Org DB (using SQL) and calls the SSRS webservice to publish the reports.
You can look at the public methods (ConfigureReports and OrganizationPublishReportsScaleGroup in Microsoft.Crm.Setup.Server.Utility (located in the same directory as PublishReports.exe) but this is completely undocumented and unsupported. I'm not sure it would work.
I have had some problems with Team Foundation Server 2012.
I have managed to recreate the reporting services and now have a SQL Server Reporting Services page to go to from TFS.
However it does not have any reports in it.
How do I go about recreating the ones that come with the process template?
TFS is being used for source control and planning at the moment so I don't want to start from scratch.
If your TFS had already been connected to SSRS before creating the team project, these reports would have been created automatically. Since you have connected it after the fact, I would recommend you use the TFS Power Tools (make sure you download the correct version for you TFS installation) and run the tfpt addprojectreports command. You can run the command with the /? switch for details on how to use it.