Joel Greijer

Default behavior of sql server install is to lock down ability to set ntfs rights on sqlbackup folder to unlock this you have to run the following as admin. This will transfer ownership to administrator for subfolder takeown /f c:\sqlbackup /a /r /d y Use at your own risk

Due to some nasty bugs in invoke-sqlcmd wrapper in powershell we must use the following workaround to be able to pass multiple parameters/variables to sqlcmd.exe from powershell $parameterizedCmd = 'sqlcmd -b -E -I -S . -d master -i "script.sql"' + ' -v Parameter1="' +$PsParameter1+ '"' + ' -v Parameter2="' +$PsParameter2+ '"' write-verbose $parameterizedCmd # invoke-expression and invoke-sqlcmd are insanely bugged # workaround by executing via cmd /c instead & cmd /c $parameterizedCmd

IgnoreFailure RedirectRowsToError OutputFailComponent RedirectRowsToNoMatchOutput LookupNoMatchBehavior NoMatchBehavior

When making changes to an existing report and publishing it to a Sql Server Reporting Services 2016 instance. The changes are not showing up when you refresh your browser throught the report manager or the report service url. I started noticing this problem when making changes to data source or data sets embedded within a report. The errors caused was something like Microsoft.Reporting.WebForms.ReportServerException: The data source 'DataSourceName' cannot be found. (rsDataSourceNotFound) or The report execution [random number] has expired or cannot be found. (rsExecutionNotFound) The cause of this seem to be that reporting services caches your report (and embedded data sources) for your session. This cache is not correctly invalidated by consecutive deploys. You can work around this by Clearing your browser cookies from your reporting services site Using your browser incognito mode (Not tested) Disable client cookies in SSRS server properties  https://msdn.micros...