dbTalk Databases Forums  

SQL Server Analysis Services Query in a SQL Server job step

microsoft.public.sqlserver.olap microsoft.public.sqlserver.olap


Discuss SQL Server Analysis Services Query in a SQL Server job step in the microsoft.public.sqlserver.olap forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Jesse O.
 
Posts: n/a

Default SQL Server Analysis Services Query in a SQL Server job step - 08-01-2006 , 01:47 PM






I've been having an issue with a step in a job.

I have a step (SQL Server Analysis Services Query) inside of a 2005 SQL
Server job which calls an Analysis Services stored procedure. I have begin,
commit, rollback transactions all within the code.

However, if the job itself fails (for instance, broken network connection,
SQL Agent goes down), the entire processing rolls back. It's as if the step
itself is being ran as a transaction. When this happens none of the
transactions actually commit.

This has been a major stumbling block and is preventing the cube from
rolling out in production. It's quite frustrating. Any ideas?

Thanks in advance!






Call

AMO.ProcessMeasureGroupProd

(
"Sales Hourly",
"Sales",
"vFact_HourlyActivitySummaryCurrent",
"Production"
)



Reply With Quote
  #2  
Old   
Jesse O.
 
Posts: n/a

Default Re: SQL Server Analysis Services Query in a SQL Server job step - 08-03-2006 , 11:07 AM






Anyone have a clue on this?

This is stopping us from putting SSAS2005 into production.

I've been stuck on it for weeks.


"Jesse O." <jesperzz (AT) hotmail (DOT) com> wrote

Quote:
I've been having an issue with a step in a job.

I have a step (SQL Server Analysis Services Query) inside of a 2005 SQL
Server job which calls an Analysis Services stored procedure. I have
begin, commit, rollback transactions all within the code.

However, if the job itself fails (for instance, broken network connection,
SQL Agent goes down), the entire processing rolls back. It's as if the
step itself is being ran as a transaction. When this happens none of the
transactions actually commit.

This has been a major stumbling block and is preventing the cube from
rolling out in production. It's quite frustrating. Any ideas?

Thanks in advance!






Call

AMO.ProcessMeasureGroupProd

(
"Sales Hourly",
"Sales",
"vFact_HourlyActivitySummaryCurrent",
"Production"
)




Reply With Quote
  #3  
Old   
Akshai Mirchandani [MS]
 
Posts: n/a

Default Re: SQL Server Analysis Services Query in a SQL Server job step - 08-03-2006 , 02:53 PM



My guess is that each request (begin transaction, execute processing,
commit) is being executed in its own session...

I would highly recommend running SQL Profiler against Analysis Services and
check the sessions that the commands are running on.

HTH,
Akshai
--
Try out the MSDN Forums for Analysis Services at:
http://forums.microsoft.com/MSDN/Sho...ID=83&SiteID=1

This posting is provided "AS IS" with no warranties, and confers no rights
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.


"Jesse O." <jesperzz (AT) hotmail (DOT) com> wrote

Quote:
Anyone have a clue on this?

This is stopping us from putting SSAS2005 into production.

I've been stuck on it for weeks.


"Jesse O." <jesperzz (AT) hotmail (DOT) com> wrote in message
news:uwTPkrZtGHA.3552 (AT) TK2MSFTNGP03 (DOT) phx.gbl...
I've been having an issue with a step in a job.

I have a step (SQL Server Analysis Services Query) inside of a 2005 SQL
Server job which calls an Analysis Services stored procedure. I have
begin, commit, rollback transactions all within the code.

However, if the job itself fails (for instance, broken network
connection, SQL Agent goes down), the entire processing rolls back. It's
as if the step itself is being ran as a transaction. When this happens
none of the transactions actually commit.

This has been a major stumbling block and is preventing the cube from
rolling out in production. It's quite frustrating. Any ideas?

Thanks in advance!






Call

AMO.ProcessMeasureGroupProd

(
"Sales Hourly",
"Sales",
"vFact_HourlyActivitySummaryCurrent",
"Production"
)






Reply With Quote
  #4  
Old   
Jesse O.
 
Posts: n/a

Default Re: SQL Server Analysis Services Query in a SQL Server job step - 08-04-2006 , 04:05 PM



Ran a trace, and it seems that they are all running under the same session
(ConnectionID) and same SPID. Everything from the calling of the stored
procedure to the processing of the partitions. All the same ConnectionID, 7.

Any other ideas? I've been banging my head on this for awhile now.










"Akshai Mirchandani [MS]" <akshaim (AT) online (DOT) microsoft.com> wrote

Quote:
My guess is that each request (begin transaction, execute processing,
commit) is being executed in its own session...

I would highly recommend running SQL Profiler against Analysis Services
and check the sessions that the commands are running on.

HTH,
Akshai
--
Try out the MSDN Forums for Analysis Services at:
http://forums.microsoft.com/MSDN/Sho...ID=83&SiteID=1

This posting is provided "AS IS" with no warranties, and confers no rights
Please do not send email directly to this alias. This alias is for
newsgroup
purposes only.


"Jesse O." <jesperzz (AT) hotmail (DOT) com> wrote in message
news:eZQMsbxtGHA.1808 (AT) TK2MSFTNGP06 (DOT) phx.gbl...
Anyone have a clue on this?

This is stopping us from putting SSAS2005 into production.

I've been stuck on it for weeks.


"Jesse O." <jesperzz (AT) hotmail (DOT) com> wrote in message
news:uwTPkrZtGHA.3552 (AT) TK2MSFTNGP03 (DOT) phx.gbl...
I've been having an issue with a step in a job.

I have a step (SQL Server Analysis Services Query) inside of a 2005 SQL
Server job which calls an Analysis Services stored procedure. I have
begin, commit, rollback transactions all within the code.

However, if the job itself fails (for instance, broken network
connection, SQL Agent goes down), the entire processing rolls back. It's
as if the step itself is being ran as a transaction. When this happens
none of the transactions actually commit.

This has been a major stumbling block and is preventing the cube from
rolling out in production. It's quite frustrating. Any ideas?

Thanks in advance!






Call

AMO.ProcessMeasureGroupProd

(
"Sales Hourly",
"Sales",
"vFact_HourlyActivitySummaryCurrent",
"Production"
)








Reply With Quote
  #5  
Old   
Akshai Mirchandani [MS]
 
Posts: n/a

Default Re: SQL Server Analysis Services Query in a SQL Server job step - 08-04-2006 , 05:46 PM



Does Profiler show what happens when you simulate the failure? I would guess
that for some reason the session is getting cancelled or something like
that...

Thanks,
Akshai
--
Try out the MSDN Forums for Analysis Services at:
http://forums.microsoft.com/MSDN/Sho...ID=83&SiteID=1

This posting is provided "AS IS" with no warranties, and confers no rights
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.

"Jesse O." <jesperzz (AT) hotmail (DOT) com> wrote

Quote:
Ran a trace, and it seems that they are all running under the same session
(ConnectionID) and same SPID. Everything from the calling of the stored
procedure to the processing of the partitions. All the same ConnectionID,
7.

Any other ideas? I've been banging my head on this for awhile now.










"Akshai Mirchandani [MS]" <akshaim (AT) online (DOT) microsoft.com> wrote in message
news:uuw8HaztGHA.2224 (AT) TK2MSFTNGP06 (DOT) phx.gbl...
My guess is that each request (begin transaction, execute processing,
commit) is being executed in its own session...

I would highly recommend running SQL Profiler against Analysis Services
and check the sessions that the commands are running on.

HTH,
Akshai
--
Try out the MSDN Forums for Analysis Services at:
http://forums.microsoft.com/MSDN/Sho...ID=83&SiteID=1

This posting is provided "AS IS" with no warranties, and confers no
rights
Please do not send email directly to this alias. This alias is for
newsgroup
purposes only.


"Jesse O." <jesperzz (AT) hotmail (DOT) com> wrote in message
news:eZQMsbxtGHA.1808 (AT) TK2MSFTNGP06 (DOT) phx.gbl...
Anyone have a clue on this?

This is stopping us from putting SSAS2005 into production.

I've been stuck on it for weeks.


"Jesse O." <jesperzz (AT) hotmail (DOT) com> wrote in message
news:uwTPkrZtGHA.3552 (AT) TK2MSFTNGP03 (DOT) phx.gbl...
I've been having an issue with a step in a job.

I have a step (SQL Server Analysis Services Query) inside of a 2005 SQL
Server job which calls an Analysis Services stored procedure. I have
begin, commit, rollback transactions all within the code.

However, if the job itself fails (for instance, broken network
connection, SQL Agent goes down), the entire processing rolls back.
It's as if the step itself is being ran as a transaction. When this
happens none of the transactions actually commit.

This has been a major stumbling block and is preventing the cube from
rolling out in production. It's quite frustrating. Any ideas?

Thanks in advance!






Call

AMO.ProcessMeasureGroupProd

(
"Sales Hourly",
"Sales",
"vFact_HourlyActivitySummaryCurrent",
"Production"
)










Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.