Does analysis service process task honor dynamic connections?

simple question.. I have a ssis package which contains analysis service process task.. it went well in the dev env. Now, I've deployed to production and connection manager was set by configuration tables.. however, it seems to me that the connection manager
on production is still pointing to the dev env... any workaround?
thanks
--Currently using Reporting Service 2000; Visual Studio .NET 2003; Visual Source Safe SSIS 2008 SSAS 2008, SVN --

Hi cat_ca,
To achieve your goal, we can combine the Environment variable Configuration with SQL Server Configuration. In short, we can create an Environment variable type Configuration to define the connection string for the Connection Manager that is used by a SQL
Server Configuration to connect to the SQL Server configuration table. To create such an Environment variable Configuration, we need to create a system Environment variable on each server to host the connection string for the corresponding connection manager
such as:
Data Source=ServerName;Initial Catalog=TestDB;Provider=SQLNCLI11.1;Integrated Security=SSPI;Auto Translate=False;
Besides, we need to make sure the Environment variable Configuration is above the SQL Server Configurations in the Package Configurations Organizer list.
Reference:
http://amenjonathan.wordpress.com/2010/12/13/creating-a-solid-ssis-etl-solution-part-2-%E2%80%93-package-configurations/
Regards,
Mike Yin
If you have any feedback on our support, please click here
Mike Yin
TechNet Community Support

Similar Messages

SSIS Analysis Services Processing Task - which object is being processed?

Hi
I've just fallen down the hole dug by a gotcha in the SSIS Analysis Services Processing task (let's call it the ASPT as it's too long to type).
I was doing testing yesterday, targeting a test database. The way things are set up here is that we have two structurally-identical databases (let's call them SSASLive and SSASTest) on the same SSAS server.
The SSIS package includes an Analysis Services Processing task that processes a partition of a measure group in a cube.
So I changed the properties of the AS Connection Manager in the package to point to database SSASTest. Then, because I'm paranoid, and don't trust the Editor for the ASPT, I edited the object to be processed, by deleting the existing object from the
list and re-adding it (going down the tree: database SSASTest, cube TheCube, measure group TheMassiveMeasureGroup, partition CurrentMonth).
This is an annoying necessity, because: the ASPT editor doesn't allow you to see exactly what the object(s) in the list to be processed are, by e.g. double-clicking on them. All you can see is the lowest-level object name, which could be just
"Current Month". Current Month what? There's no way of telling.
Test worked fine. I made sure the AS Connection manager was reset to point to SSASLive, and deployed the package.
This morning, the package ran, and processed the partition in database
SSASTest. What happened? Looking in the Code view of the package, I found the XMLA behind the Processing task: the database name is literally specified in the XMLA, and completely ignores the Catalog of the AS connection. This information
is not exposed anywhere in the UI view of the package.
It's a bit like the dangerous annoyance when testing SSIS package Exec SQL tasks, where a previous developer has insisted on fully-qualifying object names: SELECT * FROM LiveDatabase.dbo.ATable. You're working with a connection to a test database,
but it makes not difference...
But at least that problem is clearly visible. I know that specifying the database name is normal in XMLA tasks: but at least the SSIS editor should allow you to see what the setting is.

No, the point is that the Connection Manager's Initial Catalog setting (whether hard-coded or set by any of the configuration methods) has no effect on the database addressed by the Analysis Services Processing task.
Steps to reproduce:
1. Create an Analysis Services database containing a cube (or select an existing one): let's call it ASDB1.
2. Make a copy of it on the same server, e.g. by backing up and restoring: let's call it ASDB_Copy
2. Set up an SSIS package with a Connection Manager pointing to ASDB1
3. Create an Analysis Services Processing task, using the Connection Manager, processing any particular SSAS object.
4. Run the package. The SSAS object in ASDB1 is processed (not the object in ASDB_Copy). (Confirm by checking the Last Processed date in SSMS, Properties).
5. Change the Connection Manager's Initial Catalog setting to point to ASDB_Copy.
6. Run the package. The SSAS object in ASDB1 is processed, not the object in ASDB_Copy. The Connection Manager's Initial Catalog setting has no effect on the AS Processing Task. Examining the Code view of the package confirms that the XMLA
behind the task specifies the database as well as the AS object. (and this database setting is still ASDB1).
The fix would be for SSIS to perform validation of AS objects referenced by the AS Processing Task whenever its Connection manager is pointed to a different database, and to update the XMLA accordingly.
Also, it would be useful to be able to see exactly what the objects listed in the Processing Task are. The information shown is just not sufficient to identify the object to the developer. I may have dozens of measure groups with a partition
called Current Month - but "Current Month" is all I can see in the editor, and there's no way to e.g. double-click on an item in the list and get the full object identification (Cube X, measure group Y, partition Current Month). Sure,
I can go and look at the XMLA, but that's fiddly: if there's going to be a wrapper around the XMLA (which is what the AS Processing Task is), then it should be unambiguous.

Analysis Services Processing Task - Error processing

Hi all,
I have a SSIS package containing an Analysis Services Processing Task. In case it fails, I want to insert the error messages in a table. I have create an SSIS package that fails because of dimension values that are not in the fact table. The package fails and
shows a number of errors in the debug window:
Error: 0xC1000007 at Create Cube, Analysis Services Execute DDL Task: Erreur interne : L'opération n'a pas abouti.
Warning: 0x811F0001 at Create Cube, Analysis Services Execute DDL Task: Erreurs dans le moteur de stockage OLAP :
Clé d'attribut introuvable lors du traitement de : Table : 'dbo_SSIS_DATA', Colonne : 'PRODCODE', Valeur : 'HUME'. L'attribut est 'PRODCODE'.
SSIS package "Step 2 - Create Cube.dtsx" finished: Failure.
However in the error list window there are 0 errors and 0 warnings.
So, why doesn't it show an error message in the error list when the package clearly fails. And how can I get the error messages from the log into a table? Thanks in advance.
Hugo

Error list does not reflect what is getting to be logged, it is more for package validation.
But the same errors will show up in the status, and the output window.
Furthermore, if your log is table bound (e.g. the sysssiserrorlog) and in the log config you chose to log the OnError events then these will be captured automatically.
Arthur
MyBlog
Twitter

SQL Server 2005 agent job runs a SSIS package ( Analysis Services Processing Task) fails

Hi,
SQL Server 2005 standard edition.
I have a SSIS package which has a Analysis Services Processing Task. I have tested the package in BIDS and it runs ok. But when I created a agent job and run it from the job it reports error:
Code: 0xC0012024 Source: Analysis Services Processing Task Description: The task "Analysis Services Processing Task" cannot run on this edition of Integration Services.
It requires a higher level edition.
This is the result of select @@version
Microsoft SQL Server 2005 - 9.00.4035.00 (Intel X86) Nov 24 2008 13:01:59 Copyright (c) 1988-2005 Microsoft Corporation Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
Any idea?

Hi,
SQL Server 2005 standard edition.
I have a SSIS package which has a Analysis Services Processing Task. I have tested the package in BIDS and it runs ok. But when I created a agent job and run it from the job it reports error:
Code: 0xC0012024 Source: Analysis Services Processing Task Description: The task "Analysis Services Processing Task" cannot run on this edition of Integration Services. It
requires a higher level edition.
This is the result of select @@version
Microsoft SQL Server 2005 - 9.00.4035.00 (Intel X86) Nov 24 2008 13:01:59 Copyright (c) 1988-2005 Microsoft Corporation Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
Any idea?
Anyway, I have found a work around:
http://technet.microsoft.com/en-us/library/ff929186.aspx

Analysis Service Process Task Connection Manager

hi there, I was trying to use this Process Task inside SSIS to process Dimensions and partitions. The connection string for the AS connection manager is through a configuration file and value is
Data Source=10.50.30.71;Initial Catalog=ORDERDW;Provider=MSOLAP.5;
(Notice that there is no user name and password provided)
To my surprise, when I run it under SSDT 2012, the connection was tested ok and package was actually runnning withour error? Why as it does not make any sense? Under which credentials is this package running as it definitely needs username/password
to connect to AS server. Thanks
The package protection level is using default which is encryptSensitiveWithUserKey
--Currently using Reporting Service 2000; Visual Studio .NET 2003; Visual Source Safe SSIS 2008 SSAS 2008, SVN --

To my surprise, when I run it under SSDT 2012, the connection was tested ok and package was actually runnning withour error? Why as it does not make any sense?
By Default the Windows Credentials are use to logon to SSAS and I guess you have permissions to logon? So where exactly do you see an issue here?
Olaf Helper
[ Blog] [ Xing] [ MVP]

Dynamically set Analysis Services Connection Manager in a Fooreach loop [SSIS 2008]

I am storing connection strings for "Analysis Services Connection Manager" in a database table and on run time i am fetching them all, storing in an object and iterating through them inside a Foreach loop. Variable gets updated with a new connection
string in each iteration but somehow my "Analysis Services Processing Task" fails with "Invalid Connection String" Error.
Is there any way we can set set Analysis Services Connection Manager Dynamically. I can done this with OLEDB connections and that works. But somehow it's not working for Analysis Services Connection manager. Can anyone please share his/her experience ?
Many thanks
Saadat

See if this helps http://kamakshisuram.wordpress.com/working-with-ssas/ssas-connection-string-dynamically/
The trick is in using a configuration
Arthur My Blog

Permanently change default error configuration in Analysis Services 2005

Hi,
Currently, I am working on a BPC 5.1 application. The data for this application is loaded(inserted via SQL statement) right to the FACT table and then a full process is run for that cube via an SSIS package using the Analysis Services Processing Task. Often records are loaded this way where a dimension member for some of the records has not been added to the Account dimension yet. These records after loading are considered 'orphan records' until the accounts are added to the account dimension.
This loading process is used because of the volume of records loaded(over 2 million at a time) and the timing of the company's business process. They will receive data sometimes weeks before the account dimension is updated in BPC with the new dimension members.
If I try and process the application from the BPC Administration area with these orphan records in the FACT table, the processing stops and an error displays. Then when I process the cube from Analysis services, an error is displayed telling me that orphan data was found.
A temporary work-around is to go into the cube properties in Analysis Services 2005, click on Error Configuration, uncheck 'Use default error configuration' and select 'Ignore errors'. Then you can process the application from BPC's Administration page successfully. But, the problem is that after processing the application successfully, the Analysis Services Error Configuration automatically switches back from 'Ignore errors' to 'Use default error configuration'.
Does anyone have any suggestions on how to permanently keep the 'Ignore errors' configuration selected so it does not automatically switch back to 'Use default error configuration'? Prior to BPC 5.0 this was not occurring.
Also, does anyone know why this was changed in BPC 5.0/5.1?
Thanks,
Glenn

Hi Glenn,
I understood the problem but I can say that it was a bad migration of appset from 4.2 to 5.0.
Any way they are using a dts package to import data into our fact table. That's means they have to add another step into that package where they have to do the verfications of records before to insert into fact table. Verfications can be done using the same mechanism from our standard import. Just edit that package and add similar steps into customer package.
Attention you need somebody with experience developing DTS packages with for BPC to avoid other problems.
One of big benefits from 5.X compare with 4.2 was the fact that we are able to use optimization schema and aggregations for cubes.
Heaving that orphan records it is not possible to use optimization schema for cubes and you are not able to create good aggregation into your cube.
So my idea is to provide all these information to customer and to try to modify that package instead to enable that option which can cause many other issues.
Sorin

Localhost - Analysis Services Question

Hi folks,
I have a SQL Server named instance called (mymachine)\Tuesday that was installed with SQL Server Developer so I could run Analysis Services.   My original installation was done in SQL Express.   When I try to deploy a Analysis Services
Project I change the connection string from the default - localhost to the named instance (mymachine)\Tuesday.   I get the following error:
Error 62 The project could not be deployed to the 'localhost' server because of the following connectivity problems : A connection cannot be made. Ensure that the server is running. To verify or update the name of the target
server, right-click on the project in Solution Explorer, select Project Properties, click on the Deployment tab, and then enter the name of the server.  0 0
Why does the connection string have to be set to localhost?
Is the localhost connection string my original instance in SQL Express?
Can I make my Developer edition (mymachine)\Tuesday the localhost?
Can I deploy to my Developer named instance (mymachine)\Tuesday instead of localhost?
Thanks for your patience!

Hi Sorna,
I did try that, but I still got errors,
Here they are, if this tells you anything:
Error 62 Internal error: The operation terminated unsuccessfully.  0 0
Error 63 Server: The operation has been cancelled.  0 0
Error 64 Internal error: The operation terminated unsuccessfully.  0 0
Error 65 Internal error: The operation terminated unsuccessfully.  0 0
Error 66 Internal error: The operation terminated unsuccessfully.  0 0
Error 67 OLE DB error: OLE DB or ODBC error: Login failed for user 'DPS\I4X464D1$'.; 28000.  0 0
Error 68 Errors in the high-level relational engine. A connection could not be made to the data source with the DataSourceID of 'Adventure Works DW', Name of 'Adventure Works DW'.  0 0
Error 69 Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'Targeted Mailing ~MC-Customer Key', Name of 'Targeted Mailing ~MC-Customer Key' was being processed.  0 0
Error 70 Errors in the OLAP storage engine: An error occurred while the 'Bike Buyer' attribute of the 'Targeted Mailing ~MC-Customer Key' dimension from the 'Adventure Works DW2' database was being processed.  0 0
Error 71 OLE DB error: OLE DB or ODBC error: Login failed for user 'DPS\I4X464D1$'.; 28000.  0 0
Error 72 Errors in the high-level relational engine. A connection could not be made to the data source with the DataSourceID of 'Adventure Works DW', Name of 'Adventure Works DW'.  0 0
Error 73 Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'Targeted Mailing ~MC-Customer Key', Name of 'Targeted Mailing ~MC-Customer Key' was being processed.  0 0
Error 74 Errors in the OLAP storage engine: An error occurred while the 'Age' attribute of the 'Targeted Mailing ~MC-Customer Key' dimension from the 'Adventure Works DW2' database was being processed.  0 0
I'm at a loss!   I cannot get a project to deploy sucsessfully to save my life. Any idea where to go from here?
Thanks

Using UNC Path With Execute Process Task

I have an Execute Process task in which the process can either delete, get or put files to an SFTP site. The executeable takes arguments in the following format:
"host" "user" "password" "put" "full local path/filename" "full remote path/filename"
I have the task configured as follows:
RequireFullFileName: True
Executeable: \\server\groups\Development\ETLFiles\ETL_Utilities\ocsshhelper\ocsshhelper.exe
Arguments: sftp user password \\server\groups\Developmement\ETLFiles\ETL_Data_Files\CT_FS_Export_20081113.csv stateExport\export
WorkingDirectory: \\server\groups\Development\ETLFiles\ETL_Utilities\ocsshhelper
WindowStyle: Hidden
Arguments, Executeable and WorkingDirectory have been configured as Expressions. When I execute the package in BIDS from my Windows XP SP3 machine, The task fails with the following error:
[Execute Process Task] Error: In Executing "\\server\groups\Development\ETLFiles\ETL_Utilities\ocSSHHelper\ocsshhelper.exe" "sftp user password put \\server\groups\Development\ETLFiles\ETL_Data_Files\CT_FS_Export_20081113.csv stateExport\export" at "\\server\groups\Development\ETLFiles\ETL_Utilities\ocSSHHelper", The process exit code was "-532459699" while the expected was "0".
My domain account has 'effective' full control rights to the location of ocsshhelper.exe.
It could be that the executable does not support UNC paths, and I'm checking that. I have another package that uses this same application, but uses the physical path, and there are no problems. Does the Execute Process task have issues with UNC paths?
Thank you for your help
cdun2

Actually it doesn't work properly in SQL Server 2008 R2. I have a similar EP task. If I set the working directory to \\server\share\subdir the task fails. However, if I map a drive latter to the \\server\share and set working directory to <drive>:\subdir
it works

What to configure in MS SQL 2008 Analysis Services

Hello
I have several cubes in MS Analysis Services 2008 that are available for users in Excel. I am trying to configure a universe in IDT (Edge 4.1 ) but cannot add it in IDT when i create a new olap connection (XMLA). I add the parameters (authentication , server , user name , password, language ,) but it appears blank in the cube selection. I followed the instructions in Information design tool 4.0: Create a connection to an OLAP data source
How should i configure Analysis services to be able to connect to it from th IDT ?
Regards
Hector

Purchase SQL Server 2014 (or 2012) Developer Edition for around $50 (2008 may no longer be available). Install it. Also install AdventureWorks2012 sample database.
SQL Server Management Studio is part of the client tools installation. SSMS is your learning and later working environment.
SSMS Object Explorer provides you access to all of the database objects.
Practice T-SQL scripts:
http://www.sqlusa.com/bestpractices/
Kalman Toth Database & OLAP Architect
SQL Server 2014 Design & Programming
New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012

How to use one dynamic connection managers for multiple parallel data flow tasks

hi there:
I have 6 databases residing on the same server. What I want to do is call a store procedure with identical name on each database dbo schema and transport results to a centralized place. The key is to have those SPs run in parallel instead
of in sequence as each SP may take around 10 mins to finish.
The simplest way is to create 6 OLE DB connection managers and create 6 DFT tasks. However, I do not want to maintain 6 OLE DB connection managers as there is a chance to have more connection managers.
What I did so far is to create a OLD DB connection manager and use expression to set up connectionString properties so that it will get populated by variables at run time. It is fine when running all SPs in a Foreach Loop Container. However, it takes
around 60 mins to finish.
When I try to run it in parallel ( basically created 6 DFTs but use only one Dynamic Connection Manager), the connection string gets confused therefore all DFT tasks failed.
Does anyone here have some experience on this topic?
Thanks
hui
--Currently using Reporting Service 2000; Visual Studio .NET 2003; Visual Source Safe SSIS 2008 SSAS 2008, SVN --

Yes, basically, on the connectionString property of ONE OLEDB, you are using an expression to supply value and this expression is pointing to a variable.
In this case , you can update this variable from a table which contains many connection strings. It's good if you want to execute Store procedures in a sequential order. When in parallel mode, this will cause issues as connectionString gets overwritten.
I am thinking about using script task to exec sp.
The whole idea is that I do not want to maintain a large number of Connection Managers.
Hope it helps
--Currently using Reporting Service 2000; Visual Studio .NET 2003; Visual Source Safe SSIS 2008 SSAS 2008, SVN --
So you are not able to run parallel executions using same conn mgmr, even with dynamic connectionstring, is that correct? Yes, script task will be a way to go if you wish to execute it in parallel, you may connect to SS and query the proper conn string with
SELECT/WHERE clause in each script > pass it to a script variable > use that script variable and execute the proc. This will require only two things to change in each script, the WHERE condition to get the conn string and the proc name (you may even
get the proc names the same way you get conn string) and everything else will be same. Let us know how that goes.
Hope no two or more procs doing insert/update/delete on the same tables.

Analysis Services Execute DDL Task Internal error

Hi all,
I need help in solving this sporadic problem... the dimension below (blanked out as xxxx) is based on a view. The cube processes fine many times - but fails - abruptly once a week... it's being called from a sql job.
Any ideas? Thanks in advance!!
Error: 2010-06-28 15:45:17.69     Code: 0xC1000007     Source: xxxxxxx Analysis Services Execute DDL Task     Description: Internal error: The operation terminated unsuccessfully. End Error
Error: 2010-06-28 15:45:17.69     Code: 0xC11F000D     Source: xxxxxxx Analysis Services Execute DDL Task     Description: Errors in the OLAP storage engine: An error occurred while the 'xxxxx' attribute
of the 'xxxxx' dimension from the 'xxxxxx' database was being processed. End Error Error: 2010-06-28 15:45:17.69     Code: 0xC11F0006     Source: xxxxxxx Analysis Services Execute DDL Task
Description: Errors in the OLAP storage engine: The process operation ended because the number of errors encountered during processing reached the defined limit of allowable errors for the operation. End Error Error: 2010-06-28 15:45:17.69
Code: 0xC11C0002     Source: xxxxxx Analysis Services Execute DDL Task     Description: Server: The operation has been cancelled. End Error DTExec: The package execution returned DTSER_FAILURE (1).
Started: 3:45:00 PM Finished: 3:45:17 PM Elapsed: 17.328 seconds. The package execution failed. The step failed.
Harsh B

(From http://msdn.microsoft.com/en-us/library/cc966526.aspx)
"ExternalCommandTimeout is a server property that is used to set the number of seconds that SSAS should wait to time out when issuing commands to external data sources, such as relational and other OLAP sources."
"ExternalConnectionTimeout is a server property that is used to set the number of seconds, by default, that SSAS should wait to time out when connecting to external data sources, such as relational and other OLAP sources."
What you set it to, it's absolutely up to you... But as I see it in your log, your task failed in 17 and 9 seconds... So I think you can multiply the values by 10, I guess the situation won't change... But it is worth to check it at least.
So... How often your fact table gets new (degenerate) dimension reference values? Is it a process update, or a process full command? I really would like to see it :)
-- Zoltán Horváth
-- MCITP SQL Server Business Intelligence Developer 2005, 2008
-- Please mark posts as answered or helpful where appropriate.

Dynamic Parameters in MS Analysis Services and BPC

Hello Experts !
I need to execute a BPC Package, but in Microsoft Analysis Services I'm not able to have dynamic parameters, so I have to do it manually every time, because of the following problem when I try to execute it in Source Editor on Analysis Services.
"Parameter cannot be extracted from the SQL Command. The provider might not help to parse parameter information from the commnand"
The source is Sybase OLEDB
Best Regards,
Rodrigo

Hi Rodrigo,
I'm not sure I understood your question.
I'm refering to this: "but in Microsoft Analysis Services I'm not able to have dynamic parameters"
What do you mean?
Are we speaking about tasks to process cube or partitions of SSAS(SQL Server Analysis Services)?
Are you speakinga about tasks from SSIS (Sql Server integration services?)
Into SSIS you can build tasks to accept parameters.
You can have also tasks into SSIS which can perform actions into SSAS.
MODIFYSCRIPT variable is used to send parameters to tasks.
If you will clarify your questions then I hope I will be able to provide more details.
Kind Regards
Sorin Radulescu

Analysis Service Execute DDL Task throwing error with SourceType Variable

Hi,
I have Configuring Analysis Services Execute DDL Task to use Variable and Process Data(xmla Script) like below:
When I execute this task I get the below error message:
[Analysis Services Execute DDL Task] Error: The -->
text node at line 23, column 3 cannot appear inside the DataSource element (namespace http://schemas.microsoft.com/analysisservices/2003/engine) under Envelope/Body/Execute/Command/Batch/Parallel/Process. This element can
only have text nodes containing white-space characters.
Can anyone please let me know how to resolve this.

If I run using the sourceType "Direct Input", the Analysis Execute DDL Task runs fine, but if I use the sourcetype as variable its throws the error. And below is the xmla script
Here is my Package look and the xmla script; its failing at "ProcessAdd" Analysis Execute DDL task:
"SELECT '<Batch xmlns=\"http://schemas.microsoft.com/analysisservices/2003/engine\">
<ErrorConfiguration xmlns:xsd=\"http://www.w3.org/2001/XMLSchema\" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xmlns:ddl2=\"http://schemas.microsoft.com/analysisservices/2003/engine/2\" xmlns:ddl2_2=\"http://schemas.microsoft.com/analysisservices/2003/engine/2/2\" xmlns:ddl100_100=\"http://schemas.microsoft.com/analysisservices/2008/engine/100/100\" xmlns:ddl200=\"http://schemas.microsoft.com/analysisservices/2010/engine/200\" xmlns:ddl200_200=\"http://schemas.microsoft.com/analysisservices/2010/engine/200/200\" xmlns:ddl300=\"http://schemas.microsoft.com/analysisservices/2011/engine/300\" xmlns:ddl300_300=\"http://schemas.microsoft.com/analysisservices/2011/engine/300/300\" xmlns:ddl400=\"http://schemas.microsoft.com/analysisservices/2012/engine/400\" xmlns:ddl400_400=\"http://schemas.microsoft.com/analysisservices/2012/engine/400/400\">
<KeyNotFound>IgnoreError</KeyNotFound>
</ErrorConfiguration>
<Parallel>
<Process xmlns:xsd=\"http://www.w3.org/2001/XMLSchema\" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xmlns:ddl2=\"http://schemas.microsoft.com/analysisservices/2003/engine/2\" xmlns:ddl2_2=\"http://schemas.microsoft.com/analysisservices/2003/engine/2/2\" xmlns:ddl100_100=\"http://schemas.microsoft.com/analysisservices/2008/engine/100/100\" xmlns:ddl200=\"http://schemas.microsoft.com/analysisservices/2010/engine/200\" xmlns:ddl200_200=\"http://schemas.microsoft.com/analysisservices/2010/engine/200/200\" xmlns:ddl300=\"http://schemas.microsoft.com/analysisservices/2011/engine/300\" xmlns:ddl300_300=\"http://schemas.microsoft.com/analysisservices/2011/engine/300/300\" xmlns:ddl400=\"http://schemas.microsoft.com/analysisservices/2012/engine/400\" xmlns:ddl400_400=\"http://schemas.microsoft.com/analysisservices/2012/engine/400/400\">
<Object>
<DatabaseID>IIS_Version2</DatabaseID>
<DimensionID>Application</DimensionID>
</Object>
<Type>ProcessAdd</Type>
<DataSource xmlns:xsd=\"http://www.w3.org/2001/XMLSchema\" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xmlns:ddl2=\"http://schemas.microsoft.com/analysisservices/2003/engine/2\" xmlns:ddl2_2=\"http://schemas.microsoft.com/analysisservices/2003/engine/2/2\" xmlns:ddl100_100=\"http://schemas.microsoft.com/analysisservices/2008/engine/100/100\" xmlns:ddl200=\"http://schemas.microsoft.com/analysisservices/2010/engine/200\" xmlns:ddl200_200=\"http://schemas.microsoft.com/analysisservices/2010/engine/200/200\" xmlns:ddl300=\"http://schemas.microsoft.com/analysisservices/2011/engine/300\" xmlns:ddl300_300=\"http://schemas.microsoft.com/analysisservices/2011/engine/300/300\" xmlns:ddl400=\"http://schemas.microsoft.com/analysisservices/2012/engine/400\" xmlns:ddl400_400=\"http://schemas.microsoft.com/analysisservices/2012/engine/400/400\" xmlns:dwd=\"http://schemas.microsoft.com/DataWarehouse/Designer/1.0\" xsi:type=\"RelationalDataSource\" dwd:design-time-name=\"1a3cb292-9bce-4c59-a182-177d6b3506ff\" xmlns=\"http://schemas.microsoft.com/analysisservices/2003/engine\">
<ID>IISDW</ID>
<Name>IISDW</Name>
<ConnectionString>Provider=SQLNCLI11.1;Data Source=CO1MSFTSQLHKT02;Integrated Security=SSPI;Initial Catalog=IISDW</ConnectionString>
<Timeout>PT0S</Timeout>-->
</DataSource>
<DataSourceView xmlns:xsd=\"http://www.w3.org/2001/XMLSchema\" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xmlns:ddl2=\"http://schemas.microsoft.com/analysisservices/2003/engine/2\" xmlns:ddl2_2=\"http://schemas.microsoft.com/analysisservices/2003/engine/2/2\" xmlns:ddl100_100=\"http://schemas.microsoft.com/analysisservices/2008/engine/100/100\" xmlns:ddl200=\"http://schemas.microsoft.com/analysisservices/2010/engine/200\" xmlns:ddl200_200=\"http://schemas.microsoft.com/analysisservices/2010/engine/200/200\" xmlns:ddl300=\"http://schemas.microsoft.com/analysisservices/2011/engine/300\" xmlns:ddl300_300=\"http://schemas.microsoft.com/analysisservices/2011/engine/300/300\" xmlns:ddl400=\"http://schemas.microsoft.com/analysisservices/2012/engine/400\" xmlns:ddl400_400=\"http://schemas.microsoft.com/analysisservices/2012/engine/400/400\" xmlns:dwd=\"http://schemas.microsoft.com/DataWarehouse/Designer/1.0\" dwd:design-time-name=\"b0b61205-c64d-4e34-afae-6d4d48b93fb3\" xmlns=\"http://schemas.microsoft.com/analysisservices/2003/engine\">
<ID>IISDW</ID>
<Name>IISDW</Name>
<DataSourceID>IISDW</DataSourceID>
<Schema>
<xs:schema id=\"IISDW_x0020_1\" xmlns=\"\" xmlns:xs=\"http://www.w3.org/2001/XMLSchema\" xmlns:msdata=\"urn:schemas-microsoft-com:xml-msdata\" xmlns:msprop=\"urn:schemas-microsoft-com:xml-msprop\">
<xs:element name=\"IISDW_x0020_1\" msdata:IsDataSet=\"true\" msdata:UseCurrentLocale=\"true\" msprop:design-time-name=\"72037318-e316-469d-9a45-a10c77709b39\">
<xs:complexType>
<xs:choice minOccurs=\"0\" maxOccurs=\"unbounded\">
<xs:element name=\"Application\" msprop:design-time-name=\"7f579e7e-e8b7-4a9d-8a93-a255fccbbfbe\" msprop:IsLogical=\"True\" msprop:FriendlyName=\"Application\" msprop:DbTableName=\"Application\" msprop:TableType=\"View\" msprop:Description=\"\" msprop:QueryDefinition=\"SELECT a.Application, DATEADD([hour], DATEDIFF([hour], 0, a.[Timestamp]), 0) AS [Timestamp], a.ServerName, CAST(a.ServerName AS char(3)) AS DataCenter, a.CS_URI_Stem, CAST(HashBytes(''MD5'', 
 a.Application + a.ServerName + a.CS_URI_Stem + CAST(DATEADD([hour], DATEDIFF([hour], 0, a.[Timestamp]), 0) AS varchar(24))) AS uniqueidentifier) AS Server_URI_Identity
FROM IIS_6_OLD AS a LEFT OUTER JOIN
 Dimension_Pointer AS b ON a.Application = b.Application
WHERE (b.ProcessedFlag = 0) AND (a.Application IN ("+(DT_WSTR,100) @[User::strDistinctApplication]+"))
GROUP BY a.Application, DATEADD([hour], DATEDIFF([hour], 0, a.[Timestamp]), 0), a.ServerName, a.CS_URI_Stem\" msprop:QueryBuilder=\"SpecificQueryBuilder\">
<xs:complexType>
<xs:sequence>
<xs:element name=\"Application\" msprop:design-time-name=\"f3074e98-4a82-4bc5-a818-916203f7758b\" msprop:DbColumnName=\"Application\" msprop:FriendlyName=\"Application\" minOccurs=\"0\">
<xs:simpleType>
<xs:restriction base=\"xs:string\">
<xs:maxLength value=\"255\" />
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name=\"Timestamp\" msdata:ReadOnly=\"true\" msprop:design-time-name=\"2662e3a8-8b1a-4d77-aecb-575329b84dc1\" msprop:DbColumnName=\"Timestamp\" msprop:FriendlyName=\"Timestamp\" type=\"xs:dateTime\" />
<xs:element name=\"ServerName\" msprop:design-time-name=\"ced26d49-cd6e-4073-a40c-ff5ef70e4ef1\" msprop:DbColumnName=\"ServerName\" msprop:FriendlyName=\"ServerName\" minOccurs=\"0\">
<xs:simpleType>
<xs:restriction base=\"xs:string\">
<xs:maxLength value=\"255\" />
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name=\"DataCenter\" msdata:ReadOnly=\"true\" msprop:design-time-name=\"4583e15a-dcf1-45a2-a30b-bd142ca8b778\" msprop:DbColumnName=\"DataCenter\" msprop:FriendlyName=\"DataCenter\" minOccurs=\"0\">
<xs:simpleType>
<xs:restriction base=\"xs:string\">
<xs:maxLength value=\"3\" />
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name=\"CS_URI_Stem\" msprop:design-time-name=\"10db5a79-8d50-49d2-9376-a3b4d19864b9\" msprop:DbColumnName=\"CS_URI_Stem\" msprop:FriendlyName=\"CS_URI_Stem\" minOccurs=\"0\">
<xs:simpleType>
<xs:restriction base=\"xs:string\">
<xs:maxLength value=\"4000\" />
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name=\"Server_URI_Identity\" msdata:DataType=\"System.Guid, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089\" msdata:ReadOnly=\"true\" msprop:design-time-name=\"018ede0a-e15e-47c2-851b-f4431e8c839c\" msprop:DbColumnName=\"Server_URI_Identity\" msprop:FriendlyName=\"Server_URI_Identity\" type=\"xs:string\" />
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:choice>
</xs:complexType>
<xs:unique name=\"Constraint1\" msprop:IsLogical=\"True\" msdata:PrimaryKey=\"true\">
<xs:selector xpath=\".//Application\" />
<xs:field xpath=\"Server_URI_Identity\" />
<xs:field xpath=\"Timestamp\" />
</xs:unique>
</xs:element>
</xs:schema>
<IISDW_x0020_1 xmlns=\"\" />
</Schema>
</DataSourceView>
<WriteBackTableCreation>UseExisting</WriteBackTableCreation>
</Process>
</Parallel>
</Batch>' as XMLAScript_ProcessData"

SQL Server analysis service command does not retry in agent job

Hello,
I'm working on SQL Server 2008 R2 version. I have scheduled a SQL server agent job to process analysis service cube using an analysis service command. Sometimes this job fails due to network load. So I set this job to retry 2 times after 10 mins interval.
There were no retry attempts when job failed. There was no error message.
I simulated this scenario using simple analysis service command which I intentionally set to fail. That's right. It's not retrying for analysis service commands. Any workaround for this ? any suggestions ?
Thanks in advance.

Hi Anush87,
In your scenario, you had set that the step to retry 2 times after 10 mins interval. However, there were no any retry attempts when job failed, and you can reproduce this issue, right?
Since there is no any error message, it's hard to give you the root reason that cause this issue. Based on my research, so many other people had encountered this issue which you can see on the link below
http://social.technet.microsoft.com/Forums/en-US/543acccb-f107-420b-9652-53856c9137bb/sql-server-agent-job-retry-not-working?forum=sqldatabaseengine, you can you can submit a feedback at the link below
http://connect.microsoft.com/SQLServer/Feedback
So that Microsoft will confirm that if this issue is a bug in SQL Server Agent job.
However, in order to troubleshoot this issue, you can query Agent job information to ensure the job configure settings are correct, you can refer to the link below to check it.
http://www.mssqltips.com/sqlservertip/2561/querying-sql-server-agent-job-information/
http://www.sqlservercentral.com/blogs/hugo/2009/05/27/configuring-auto-retry-on-sql-server-agent/
Hope this helps.
Regards,
Charlie Liao
TechNet Community Support

Does analysis service process task honor dynamic connections?

Similar Messages

Maybe you are looking for