SSIS Package and cancel deletion of Dimension members

I am working on a SSIS package for dimension automation for BPC 10. Is there a way to have the ability to stop the processing from occurring if Deleted Members are detected?
Thanks.

i have the same problem.
when i use ssis, if, by mistake, i delete an item in one dimension, all rows in the fact table are deleted.
Need help!
Please

Similar Messages

How to deploy SSIS packages and jobs that run the package?

I am fairly new to deploying SSIS packages. We are migrating servers and I need to deploy the packages to the new dev and prod servers. Can you please walk me through this? Also is there a configuration through which we can specify connection strings so
that it is not dependent on a particular environment?
Anonymous

Hi Devcoder,
As Visakh16 suggested above, we can use deployment utility to deploy SSIS packages to production server. Here are some good articles regarding this topi for your reference, please see:
Deploying SSIS Packages on to Production Server:
http://sqlbiblog.blogspot.com/2011/02/deploying-ssis-packages-on-to.html
Package Deployment (SSIS):
http://msdn.microsoft.com/en-us/library/ms137592.aspx
If you have any feedback on our support, please click
here.
Elvis Long
TechNet Community Support

Upgrade Preparation: How to map applications, DTS packages, SSIS packages and reports to databases

Hi,
I am on the initial phase of upgrading SQL Server 2005 to SQL Server 2012. Right now, I'm taking as much inventory as I can from our current server, SQL Server 2005. If anyone could help me, how can I map the following:
Map applications to databases
Map DTS packages to databases
Map SSIS packages to databases
Map reports to databases
Thank you!

Some questions and suggestions:
How are we planning to upgrade whether in-place\parallel\others?
Will this be with HA[Clustered one] or with standalone?
Do you have time to do actual migration from now on and you will need to setup the environment for end to end testing for application validation so that all differences between application or system variables can be known before actual deployment?
Also, it will be good to check with Upgrade Advisor for below pointers preparedness too.
Map applications to databases: If you have already need to setup databases and logins for each and every applications then your mapping to database for applications will be lot easier and you will have less challenge.
Map DTS packages to databases: Good link to check
https://www.simple-talk.com/sql/ssis/dts-to-ssis-migration/
Map SSIS packages to databases: Good link to check
http://www.experts-exchange.com/Database/MS-SQL-Server/Q_28340818.html http://www.sqlservercentral.com/Forums/Topic1531839-2799-1.aspx
Map reports to databases -- Good link for Reporting Services if you meant that:
http://msdn.microsoft.com/en-us/library/ms143747.aspx
http://www.mssqltips.com/sqlservertip/2627/migrating-sql-reporting-services-to-a-new-server/
Good link to check other thing as well :
http://thomaslarock.com/2013/03/upgrading-to-sql-2012-ten-things-you-dont-want-to-miss/
Santosh Singh

Priority solution between SSIS Package and CLR Proc.

I have to implement a solution for some logical ETL process among SQL Servers(source 2008 & dest. 2005). Solution can be achieved by using SSIS or CLR. Which one should be implemented and why? Please suggest.
PGupta

I have copied the SSIS package from a server to my local drive for modification. In Server it was in D drive. My local one is in C Drive. I was getting the same error message. After looking at more detail, I found that in the Configuration of the Project,
the Output Path was specified to D:\XXXX and DeploymentOutputPath also has D:\XXX. After changing both of them to C:\XXXX, it is working fine. You need to specify those path correctly as your project path.
You can find those two fields (variable) by going through following steps:
1. Right click on Project
2. Select Properties
3. From the Left pane click on Build and Right pane will show OutputPath
4. From the Left pane click on Deployment Utility and Right pane will show DeploymentOutputPath

SSIS package and sql agent issue

Hi guys, I don't know if is the perfect place but I've got a question about running SSIS package from the Job Agent. The problem that I am having this issue: Access Denied.
What I do is to put the package in a folder in my network where everyone is able to read and write. Of course if I double click the package it's works, bear in mind that the package write in the Database FORUM and I am the only one that has access to the
database. So if one of my colleague try it doesn't work. But, two questions:
1) SQL agent need to be configured as a normal user or automatically if you put a package in SQL Agent it can write everywhere?
2)Most important, in network terms should I ask to the administrator to set up NAMENETWORK\NAMESERVER$ in order to read/write from the table where the package is?

Sorry...resolved. I set up a proxy with my credentials and now it's running good.

Updating dimension with SSIS Package

Hello there, I have a dimension thats basically taking all the rows of two other dimensions, but it needs to b updated frequently. I need to build a SSIS package that can do this. Its easy to build one that updates the SQL table, but how to make those changes appear on BPC Admin side??? I tried updating both mbr and dim tables but nothing seems to work. please advise. thanks.

Hi,
You need to update your mbr table ONLY, and then add a BPC task called "Admin Task" to your package and choose the "Process Dimension" option. In any case, from your SSIS package, your dimension should be processed, and your application as well.
This process is moving members from the "mbr" table into the "dim" table.
After that, when relogging to BPC, your changes should be reflected.
Hope this helps.
Kind Regards,
Patrick

Deleting dimension members

We have an AW with cubes refreshing every day. Fast solve of these cubes with incremental set of data finishes usually within an hour or two.
Our recent requirement needs for us to remove some old facts as well as a few dimension members. The facts can be cleared but we noticed that deleting dimension members (using synch load) is causing a full cube solve due to changed relations. With the amount of data existing in this AW, full solve takes about 2 days to complete. Deleting dimension members for which we never ever loaded any facts also causes the same result as above.
I was wondering if there is any way we can delete these dimension members without triggering a full cube solve.
Another question is if it is possible to update dimension primary keys inside of the AW?
Any help is really appreciated.
Database Version 11.2.0.3

These types of questions have been answered in the past by David Greenfield.
There are two ways to delete a dimension member through commands.
(1). OLAP dml command "REMOVE_DIMENSION_MEMBER" explained here: http://docs.oracle.com/cd/E11882_01/olap.112/e17122/dml_commands_2042.htm#OLADM2692
OR
(2). dbms_cube.build command:
exec dbms_cube.build(q'! "TIME" USING (DELETE FROM DIMENSION WHERE MEMBER = 'APR-2011') !');
Take a look at this old post, where David Greenfield explained it.
https://forums.oracle.com/message/9426946
There is no way to rename a dimension member in a standard-form analytical workspace. There is "MAINTAIN RENAME" olap dml command, but it will not work with dimensions created through AWM. You can add the new dimension member, then copy cube data associated with old/existing member to the new member and then delete the old member.
For cube copy data example, take a look at these old (15-Feb-2011, 16-Feb-2011 and 17-Feb-2011) posts by David Greenfield:
https://forums.oracle.com/thread/2176409

DTEXEC does not fail when SSIS package fails

I need to run my SSIS 2012 packages through the catalog with DTEXEC. This works very well, except that if my SSIS package fails, DTEXEC does not fail. I need DTEXEC to fail, so my scheduler knows that there is an error.
I use the following command:
dtexec /ISServer "\SSISDB\MyFolder\MyProject\MyPackage.dtsx" /Ser MyServer /Par $Package::Partition;201412 /Env 5
When I check the status of the run in the Catalog, it is failed.
When I used SSIS 2008, I had no problem getting DTEXEC to fail when the packages failed.

I've had the same problem, and come up with the following prototype for a SQL Script which I run in our JAMS Enterprise Scheduler. It uses SSISDB stored procedures to start the SSIS package and polls every 5 seconds to report any messages, and final
status code of the package. JAMS parameters are delimited by << >> symbols, and will need to be changed for your scheduler/batch process. I guess the script could be converted to a stored procedure. I'm also hoping it will work with SQL High
Availability groups to ensure the SSIS package runs on the server that's hosting the active database.
DECLARE @execution_id BIGINT
DECLARE @status INT= 1
DECLARE @Event_Message_id BIGINT= 0
DECLARE @Last_Event_Message_id BIGINT= 0
DECLARE @message_time DATETIME2(7)
DECLARE @message NVARCHAR(MAX)
--Create a SSIS execution for the required SSIS package and return the execution_id
EXEC [SSISDB].[catalog].[create_execution] @package_name = N'<<pPackageName>>.dtsx',
    @execution_id = @execution_id OUTPUT, @folder_name = N'<<pSSISFolderName>>',
    @project_name = N'<<pSSISProjectName>>', @use32bitruntime = <<p32Bit>>, @reference_id = NULL
RAISERROR('Starting SSIS package <<pPackageName>> with execution_id %I64d on server %s',0,0,@execution_id,@@SERVERNAME) WITH NOWAIT
--Set the logging level 0-none, 1-basic (recommended), 2-performance, 3-verbose
EXEC [SSISDB].[catalog].[set_execution_parameter_value] @execution_id,
    @object_type = 50, @parameter_name = N'LOGGING_LEVEL',
    @parameter_value = <<pLogging_Level>>
--Start the package executing
EXEC [SSISDB].[catalog].[start_execution] @execution_id
WHILE @status IN ( 1, 2, 5, 8 ) --created (1), running (2), canceled (3), failed (4), pending (5), ended unexpectedly (6), succeeded (7), stopping (8), and completed (9).
    BEGIN
        WAITFOR DELAY '00:00:05'
    --Get the status to see later if we've finished
        SELECT @status = status
        FROM    SSISDB.catalog.executions
        WHERE   execution_id = @execution_id
    --Are there any event messages since we last reported any?
        DECLARE curEventMessages CURSOR FAST_FORWARD
        FOR
            SELECT event_message_id ,
                    message_time ,
                    message
            FROM    SSISDB.catalog.event_messages
            WHERE   operation_id = @execution_id
                    AND event_message_id > @Last_Event_Message_id;
        OPEN curEventMessages
        FETCH NEXT FROM curEventMessages INTO @Event_Message_id, @message_time,
            @message
        WHILE @@FETCH_STATUS = 0
            BEGIN
        --We've found a message, so display it - watch out for % signs in the message, they'll cause an error if we don't replace them
                SET @message = CONVERT(NVARCHAR(MAX), @message_time, 113)
                    + ' ' + replace(@message,'%',' percent')
                RAISERROR(@message,0,0) WITH NOWAIT
                SET @Last_Event_Message_id = @Event_Message_id --Make a note that we've reported this message
                FETCH NEXT FROM curEventMessages INTO @Event_Message_id,
                    @message_time, @message
            END
        CLOSE curEventMessages
        DEALLOCATE curEventMessages
    END
--@Status indicates that package execution has finished, so let's look at the outcome, and error if there's a problem
IF @status = 7
    RAISERROR('Package Succeeded',0,0)
ELSE
    IF @status = 9
        RAISERROR('Package completed',0,0)
    ELSE
        IF @status = 3
            RAISERROR('Package Cancelled',16,1)
        ELSE
            IF @status = 4
                RAISERROR('Package failed (see error message above)',16,1)
            ELSE
                IF @status = 6
                    RAISERROR('Package ended unexpectedly',16,1)
                ELSE
                    RAISERROR('Package ended with unknown status %i',16,1,@status)

Pick out the SSIS package from a job

Hi Everyone,
I have a SQL 2k5 instance. Previously someone embedded a SSIS package in a job and I just want to look into the SSIS package to understand the logics. However, in the job property, the package source is "SQL Server" and I don't know where I can
find the package itself(actually I tried open corresponding integration service but found nothing) and make a copy. Could someone give me some advice? Thank you very much.
regards,
Oliver

Hi Jens,
Thanks for your reply. Actually 2 of the job parameters are as below:
Package Source: SQL Server
Server: DE-S-0157590\DE_S_0157590
I tried to connect to integration service "DE-S-0157590", and I expanded every folder in the object panel but didn't find any SSIS package there. Could you please give some more suggestions? Thanks a lot.
Hi Oliver_Wang,
According to your description, we need to verify if someone has delete the SSIS package which is used in your job, I recommend you run this job and check if the job can execute successfully. Or you can choose “Edit” in the job steps and check if the SSIS
package exists in select an SSIS Package Box.
If the package indeed exist, we need to verify if you choose the right SQL Server instance. In addition, when you connect to integration service, we need to verify if your login account has permission to view the SSIS package and so on. There is an article
about SQL Server Agent jobs for packages, you can review it.
http://msdn.microsoft.com/en-us/library/ms141701(v=sql.90).aspx
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support

How do I get SQL Agent to perform an FTP connection through a SSIS package?

I have created a number of SSIS packages that I am running through SQL Agent in various jobs. I have set up a Credential / Proxy for the job steps and for the most part everything runs no problem. The issue I have is with the step where I make
a connection to a FTP server and download files. In BIDS the step works fine but in SQL Agent the step times out. I presume that it has to do with the account that it is being run under but that is what I thought the Credential / Proxy was supposed
to handle (as it does for all the other steps). I am running on SQL Server 2008 R2. I have created a test job that has only one step which is to connect to the FTP server and download some text files. I have tried utilizing package configuration
files and have tried various ProtectionLevels to no avail.
Anyone have any thoughts or direction for me to take? Will continue to research and will post if I resolve this.
Thanks, Andrew

On the dev environment the ProtectionLevel is set to EncryptSensitiveWithUserKey and that is what I tried first on the prod server. Subsequently I also tried utilizing a package config file (with ProtectionLevel then of DontSaveSensitive) and have
also tried working with the ServerStorage.
For deployment I copied the relevant dtsx files to a solution on the prod server. I verified that the packages all had tested connections in the Connection Manager. I have run all the packages in the BIDS on the prod server and they all worked.
I have created a test package from scratch on the prod server to test the ftp connection. This test package runs from BIDS fine. I have set the SQL Agent file to access through the file system (no luck) and have saved the package to the SSIS Packages
and had the job step access from there (no luck either).

Is there any way to control the zoom factor so that when my SSIS Package is opened, it is entirely visible within Visual Studio?

I have formatted my SSIS Package beautifully, if I do say so myself, so that all my tasks are visible at 50% zoom. However, when I close my project and then re-open it in Visual Studio, it defaults back to 100%...YUK!
I did find this post which didn't seem to work...even to the point that no where within my xml could I even find the "PersistedZoom" Parameter. I even tried manually adding it, I couldn't find the exact syntax on it, and that didn't even work.
1. In BIDS (Visual Studio) first close all open SSIS packages / xml files to avoid confusion ...
2. Right click on the SSIS package and select the "View Code" menu item. (to open the actual xml)
3. Search for all instances of "PersistedZoom" and change the value directly to the right of it to 100 (mine
was 80 or 90 ...)
4. Now save and close the XML file.
5. Now open the SSIS package in the designer, you will notice that it is still scrolled to the bottom right!
6. Now make any small change (I scrolled to the top-left and just slightly moved a task)
7. Now save and close the designer
8. Re-open the SSIS package in the designer! and what do you know it does not start scrolled down to the bottom right anymore!
Let me know if you still have issues - but as I said I followed this same process on all my problem packages and they ALL now open correctly.
I noticed that after doing all this the PersistedZoom property disappeared from the xml, which leads me to believe that if I zoom in and out of my packages again it will probably get stuck by opening to the bottom right again ...
Can anyone help me out with this?
Thanks for your review and am hopeful for a reply.
PSULionRP

There is no way to preserve view preferences.Just remember or annotate the zoom % used in the package.
You may want to open an MS Connect item asking to add such a feature.
I can tell you it may not be implemented because a package may be opened on different size monitors.
Arthur My Blog

SQL SERVER - Error while executing SSIS package on specific environment : Connection manager - The specified module could not be found

I have deployed my SSIS packages on SQL 2008 server.
I have a .bat file which will invoke these packages and also the bat file is placed in the server where the SSIS packages are deployed.
Scenario 1:
I double clicked on the bat file to invoke the SSIS packages and ; this executed successfully
Scenario 2:
I have used the IBM Tivoli work scheduler(TWS) to invoke the bat file which in tern will invoke the ssis packges;
but when i do this i am getting the below error
Code: 0x8007007E
Source: SSIS_Master_Event_Data_Transfer Connection manager "Config DB"
Description: The specified module could not be found.
Config BD is a connection manager which will get the connection string from the config file of the SSIS package.
Please help me to resolve this issue.
Regards,
Prakash

Check you TWS jobmanrc.cmd configuration file. You may need to add a PATH environment variable in that file that includes your SQL Server file locations. When TWS jobs are executed, they may not be executing with the same
PATH variable as when you execute the SSIS outside of TWS.

SSIS package give an error if execute through SQL server agent

I have created a SSIS package in BIDS 2012. If i execute this package through sql server agent it gives the below error:
Executed as user: NT Service\SQLSERVERAGENT. Microsoft (R) SQL Server Execute Package Utility Version 11.0.2100.60 for 64-bit Copyright (C) Microsoft Corporation. All rights reserved. Started: 11:19:47 AM Error: 2015-01-20
11:19:47.83 Code: 0xC0016016 Source: Sub_Hadoop_aggregation Description: Failed to decrypt protected XML node "DTS:Password" with error 0x8009000B "Key not valid for use in specified state.".
You may not be authorized to access this information. This error occurs when there is a cryptographic error. Verify that the correct key is available. End Error Error: 2015-01-20 11:19:47.94 Code: 0xC0016016 Source:
Sub_Hadoop_aggregation Description: Failed to decrypt protected XML node "DTS:Password" with error 0x8009000B "Key not valid for use in specified state.". You may not be authorized to access this information. This error
occurs when there is a cryptographic error. Verify that the correct key is available. End Error Error: 2015-01-20 11:19:48.04 Code: 0xC0016016 Source: Sub_Hadoop_aggregation Description: Failed to
decrypt protected XML node "DTS:Password" with error 0x8009000B "Key not valid for use in specified state.". You may not be authorized to access this information. This error occurs when there is a cryptographic error. Verify that the correct
key is available. End Error Error: 2015-01-20 11:19:48.92 Code: 0xC00291EC Source: alter_keys Execute SQL Task Description: Failed to acquire connection "mstr_warehouse". Connection may not be
configured correctly or you may not have the right permissions on this connection. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 11:19:47 AM Finished: 11:19:48 AM Elapsed: 1.42 seconds.
The package execution failed. The step failed.
so i have change some properties in our package like protectionlevel change from encrypted to dontsavesensitive. After that i have created configuration file for the package and use that configuration file. It executes the package through sql server agent
smoothly.
Thanks
Azhar Khan

Hi selfdestruct80,
According to your description, you created SSIS package and it works fine. But you got the error message when the SSIS package was called from a SQL Server Agent job.
According to my knowledge, the package may not run in the following scenarios:
The current user cannot decrypt secrets from the package.
A SQL Server connection that uses integrated security fails because the current user does not have the required permissions.
File access fails because the current user does not have the required permissions to write to the file share that the connection manager accesses.
A registry-based SSIS package configuration uses the HKEY_CURRENT_USER registry keys. The HKEY_CURRENT_USER registry keys are user-specific.
A task or a connection manager requires that the current user account has correct permissions.
According to the error message, the SSIS Package ProtectionLevel property to EncryptSensitiveWithPassword as ArthurZ mentioned. To solve the problem, you need to go to Command Line tab, manually specify the paassword in SQL Agent Job with the command like below:
/FILE "\"C:\Users\xxxx\Documents\SQL Server Management Studio\SSIS\Package.dtsx\"" /DECRYPT somepassword /CHECKPOINTING OFF /REPORTING E
If you have any more questions, please feel free to ask.
Thanks,
Wendy Fu
Wendy Fu
TechNet Community Support

Error coming after using an ssis package to create an sql job

Hi
I have created an SSIS package and try to create a job on the same when i run the job it if failing an dgiving me the below error
Executed as user: xxxxx\FESGSQLA. Microsoft (R) SQL Server Execute Package Utility Version 10.50.4000.0 for 64-bit Copyright (C) Microsoft Corporation 2010. All rights reserved.    Started: 12:33:03 AM Error: 2014-03-19
00:33:03.12     Code: 0xC0011007     Source: {DD3B52A8-850A-4328-94DC-CF51B4376BCB}      Description: Unable to load the package as XML because of package does not have a valid XML format. A
specific XML parser error will be posted. End Error Error: 2014-03-19 00:33:03.12     Code: 0xC0011002     Source: {DD3B52A8-850A-4328-94DC-CF51B4376BCB}      Description: Failed
to open package file "D:\Users\xxxxxx\Desktop\I11_Load_SAP_Recon_Data.dtsx" due to error 0x80070003 "The system cannot find the path specified.". This happens when loading a package and the file cannot be opened or loaded correctly
into the XML document. This can be the result of either providing an incorrect file name was specified when calling LoadPackage or the XML file was specified and has an incorrect format. End Error Could not load package "D:\Users\H139933\Desktop\I11_Load_SAP_Recon_Data.dtsx"
because of error 0xC0011002. Description: Failed to open package file "D:\Users\xxxxxx\Desktop\I11_Load_SAP_Recon_Data.dtsx" due to error 0x80070003 "The system cannot find the path specified.". This happens when loading a package
and the file cannot be opened or loaded correctly into the XML document. This can be the result of either providing an incorrect file name was specified when calling LoadPackage or the XML file was specified and has an incorrect format. Source: {DD3B52A8-850A-4328-94DC-CF51B4376BCB}
Started: 12:33:03 AM Finished: 12:33:03 AM Elapsed: 0.046 seconds. The package could not be found. The step failed.
Please throw some light on the issue and stpes to resolve.
Thanks
Geeth If you feel that the answer which i gave you is Helpful please select it as Answer/helpful.

The package was created using a newer SSIS version than you have in the target (server).
Arthur My Blog

Schedule SSIS packages as job in SQL Server Agent errors

Hi, I am using SQL Server 2008 R2 and created few SSIS packages and schedule them using SQL Server Agent and every time I try to schedule packages via SQL Server Agent my jobs keep failing. I am using domain/ione as the owner and when I invoke the job on
ServerA let's say and the job gets executed by domain/ServerA$ and fails as it does not have enough privileges. How do I fix this issue firstly without the proxy and why is the job being executed by domain/ServerA$ when the owner & user who invokes
it is domain/ione?
Thanks in advance............
Ione

Hi Ione,
The owner of any SQL jobs should be SA or any other non-expiring account
If you do not want the proxy used, then add the needed priveleges.
The owner of the job is one, the SSIS step gets executed by the account the Agent is running under.
Arthur
MyBlog
Twitter

SSIS Package and cancel deletion of Dimension members

Similar Messages

Maybe you are looking for