New answers tagged

2

You can use sp_start_job stored procedure to start a job from any server using the server_name parameter. Passing nothing to this parameter means the job is on the local server but you should be able to pass your remote instance name and have it call the job on that server. The only thing I think is you might have to use a run as condition on the job ...


2

If you're on SQL Server Enterprise Edition: You could set up a Data-driven subscription in SSRS. On your database with the FTP/Import Job, the system database MSDB contains a table called sysjobhistory. On your SSRS server, set up a Data-driven subscription to run when the step in your FTP/Import job reports success to this table. Instructions for setting ...


1

In the parameter preference pane, there's one tab for available, and one tab for default. You can pick completely different details for each set, including different datasets, one with the available options, and one selecting just the ones you want set as defaults.


2

Assuming native mode here... The main thing you are migrating when doing the upgrade to SQL Server 2014 is the reports, subscriptions, and then your data connections. I can't think of a reason why you would need to put this database in replication just for an upgrade. Also, while it probably could be done (and work) it is not a supported method of upgrade ...


2

Microsoft describes it's support for Availability Groups with SSRS in BOL. In particular is the section titled "Report Server Databases and Availability Groups." In my experience, having ReportServer and ReportServerTempDb be part of an AG works fine in most cases, but there is some peculiar behavior with subscriptions and failover--which is described in ...


3

Find and Replace one of the desired characters, such as an Underscore, in the dataset query SQL with a non-sense string, such as "3145234jhasdf" ..... (minus the quotes). In Report Builder, create a DataSet with the resulting data. Create a Tablix with that DataSet. The headers in the Tablix will now look odd. As an example the header, "Column_One", will ...


0

I believe problem was that the report definitions no longer matched the stored procedures that were called. After I refreshed all of my reports the problem seems to be resolved. Unfortunately I can not say for sure that is the final answer as it could be up to 90 days between the last restart and as little as 4 days, so I am still waiting to remove this ...



Top 50 recent answers are included