Viewing 15 posts - 5,266 through 5,280 (of 13,872 total)
August 17, 2017 at 7:32 am
August 17, 2017 at 6:38 am
I can see nothing in the links which you provided which states that ispac files (which are the result of building an SSIS project) can be deployed to the file...
August 17, 2017 at 5:48 am
Do you have SQL Server Developer Edition installed? That should be sufficient.
August 17, 2017 at 5:45 am
Something like this should get you most of the way there:
WITH Results
AS
(
SELECT
UPPERAGE
, [First trail year] = CASE
August 16, 2017 at 2:24 pm
August 16, 2017 at 2:14 pm
August 16, 2017 at 2:10 pm
August 16, 2017 at 12:32 pm
So are you trying to connect as a SQL Server named user, by passing username and password credentials?
August 16, 2017 at 12:30 pm
Any time that an SSIS job works in SSDT, but not in SQL Agent, your first suspicion should be that there is a permissions problem.
Does the SQL Agent service/proxy...
August 16, 2017 at 10:16 am
August 16, 2017 at 9:28 am
Hello Scott
I won't download the solution just yet, because I believe I understand the issue you are having.
As I cryptically implied in my earlier message, configuration of data...
August 16, 2017 at 6:13 am
If you are working with project-level parameters and connections, your packages need to be deployed to SSISDB.
Once you have this, use SSISDB environments to configure your connections per environment.
August 16, 2017 at 5:56 am
August 15, 2017 at 9:15 am
Viewing 15 posts - 5,266 through 5,280 (of 13,872 total)