Viewing 15 posts - 1 through 15 (of 57 total)
I would create a new project based on the SSAS production instance.
https://technet.microsoft.com/en-us/library/ms365361(v=sql.105).aspx
August 31, 2016 at 12:06 pm
I don’t know why it doesn’t work, however here is how to get it to work:
Add columns between your “Operador” and “NumOrder”, copy and paste the values from existing columns...
August 16, 2016 at 2:39 pm
The display formats expect a weighted percentage to be between 0 and 1. I.e. if you want 10% to show in SSRS, then you pass the value 0.1
In Q1 you...
August 10, 2016 at 10:14 am
My guess: One of your parameters to the encryption process somehow changes value in the child package in certain scenarios.
Have you tried to log all the parameter values both from...
August 1, 2016 at 8:35 am
Since the constraint is due to TRUNCATE, you could remove the constraint while you run the package and then add it back.
Alternative is to do an incremental load on your...
July 28, 2016 at 10:45 am
Alternative and easier to maintain:
Add a SQL table with two columns, one column for the value you want, and one column for the alternate value.
Add a row for each...
July 8, 2016 at 2:08 pm
I find the use of three project parameters the easiest way to implement the option of default or manual dates. The project parameters can then be changed for the SQL...
June 14, 2016 at 12:15 pm
Lookup only allows for one condition. If you want to test for multiple conditions, use the conditional split instead.
From a readability and maintenance perspective, I would use two consecutive...
June 10, 2016 at 6:54 am
You can use Switch, Switch(Month(Fieds!Date.value)=1, “January”, Month(Fieds!Date.value)=2, “February”,…), easier to use Choose, Choose(Month(Fieds!Date.value), “January”, “February”…), a lot easier to use MonthName(Month(Fieds!Date.value)).
January 21, 2016 at 11:05 am
Easiest workaround is using the SSRS URL https://msdn.microsoft.com/en-us/library/ms153586(v=sql.110).aspx
You can use any language, like PowerShell or Scripting Task in SSIS, to send the command to SSRS.
Powershell example: http://blogs.msdn.com/b/cdndevs/archive/2015/10/14/automate-ssrs-report-generation-using-powershell.aspx
SSIS example: https://technet.microsoft.com/en-us/library/ff793463(v=sql.105).aspx
Native SSIS...
January 6, 2016 at 12:41 pm
Just to expand on Jeff’s “upsert“ comment for future reference.
This pattern can be replaced with a single “Upsert” on the source and destination table. I find the merge is...
December 15, 2015 at 12:18 pm
Yes, read the Stairway to Integration Services lesson 4: http://www.sqlservercentral.com/articles/Stairway+Series/76390/
December 15, 2015 at 9:04 am
It is done in a slightly different way.
All your reports share data connections in their environment, so once you have a deployed a data connection to an environment, you edit...
November 13, 2015 at 8:17 am
Yes, it is feasible.
I would break it down in two different steps, Request and Update, is since SSRS track all requests, you can always go back into the Report...
November 12, 2015 at 6:28 am
The problem as I see it, is that you looking at two different rows of data.
You could try with the Lookup function or the Previous function (if you have the...
November 11, 2015 at 2:16 pm
Viewing 15 posts - 1 through 15 (of 57 total)