Tag Info

New answers tagged

0

SSRS has a number of configuration files, including RSReportServer.config. Both Shared Schedules and Shared Data Sources are good things to create since they help you manage your configuration without giving each and every report it own schedule. View this as saving you some work. Of course, independent Schedules and Data Sources will likely be needed ...


5

have built my SSIS packages to check and make sure that the day isn't a holiday by comparing the date to a table that contains holidays. You can have your 1st job step as IF EXISTS (SELECT 1 FROM HolidayTable WHERE Date = GETDATE()) begin RAISERROR ('There is nothing to run as today is holiday !', 16, 1) end else print 'The job can run .. ...


0

If your data needs to be persistent over a failure & restart then a "real" table in your database would be best. You need a mechanism to isolate one user's execution of this from another's and to tidy up nicely. If data is to be disposed of if the SP crashes and will be re-created on a restart then a table-valued variable would be adequate. These are ...


1

I found the solution in case anyone else comes across this. The issue lied in the connection string property of the data source. For some reason (maybe standard, I am simply unaware of why) the connection string properties were empty after importing them to the new server. After setting them, they were able to hit the stored procedures and all reports ran ...


1

Your server has to be a member of the SharePoint farm before it will allow you to install SSRS in integrated mode. Refer to this article for more information.



Top 50 recent answers are included