Showing posts with label including. Show all posts
Showing posts with label including. Show all posts

Saturday, February 25, 2012

Question on Cube actions

Hi, all experts here,

I am having a question on cube actions. What is the easiest way for us to see all actions properties(including objects to trigger the actions, etc.), hope it is clear for your help and I am looking forward to hearing from you shortly.

Thanks a lot in advance.

With best regards,

Yours sincerely,

Hello Helen. Are you missing any information in the actions tab of the cube editor?

HTH

Thomas Ivarsson

|||

Hi, Thomas,

Thank you very much for your kind attention.

Well, I asked the question from a end-user point of view like when they browse their data from end clients like Excel 2007, rather than respectively click on each object displayed in Excel to see know available cube actions, is there any way that they can have an overview of all available cube actions on the cube they are browsing in Excel? So that they are able to have a whole idea of what actions are available on the cube.

Thank you very much again for your kind advices and I am looking forward to hearing from you shortly.

With best regards,

Yours sincerely,

|||

Hi Helen. I have not seen this option in Excel2007. I think it is only possible by right clicking a member.

Regards

Thomas Ivarsson

|||

Hi, Thomas,

Thank you very much for your very kind atttention and advices and help.

With best regards,

Yours sincerely,

|||I suppose you could shade the back color of all cells that have actions on them using a Back_Color(this) = assignment in the calc script. I personally think that would clutter a spreadsheet, but it's an option if you're desperate.|||

Hi, Furmangg, thank you very much for that. It's been very helpful advices.

With best regards,

Yours sincerely,

question on commit

Hi
i have a question about what the COMMIT command actually does
According to my understanding i thought a commit is just like including a marker and it shouldnt take time to finish.
Checkpoint is actuallly the process which writes committed transaction to the disk so that should be the one taking time.
If this is true why does BCP in take a long time at the end when its commiting all rows copied from the file
Anywhere i can go to read about what commit actually does and what checkpoint does etc
SanjaySanjay
BOL says:
COMMIT TRANSACTION
Marks the end of a successful implicit or user-defined transaction. If
@.@.TRANCOUNT is 1, COMMIT TRANSACTION makes all data modifications performed
since the start of the transaction a permanent part of the database, frees
the resources held by the connection, and decrements @.@.TRANCOUNT to 0. If
@.@.TRANCOUNT is greater than 1, COMMIT TRANSACTION decrements @.@.TRANCOUNT
only by 1.
"Sanjay" <sanjayg@.hotmail.com> wrote in message
news:A1B8DE74-8DF1-4F7C-9341-3161D1F05158@.microsoft.com...
> Hi
> i have a question about what the COMMIT command actually does
> According to my understanding i thought a commit is just like including a
marker and it shouldnt take time to finish.
> Checkpoint is actuallly the process which writes committed transaction to
the disk so that should be the one taking time.
> If this is true why does BCP in take a long time at the end when its
commiting all rows copied from the file
> Anywhere i can go to read about what commit actually does and what
checkpoint does etc
> Sanjay
>|||Hi Sanjay,
By default checkpoints happen automatically and very regularly on SQL
Server. How often a checkpoint happen is determined by the Recovery Interval
setting. If SQL Server determines that the estimate time to recover the
database by rolling forward the transactions in the transaction log is
longer than the recovery interval, it will issue a checkpoint so all the
changes are flushed to the data file and don't have to be rolled forward the
next time the database starts up.
What I think happens is that BCP makes so many changes that it automatically
triggers a checkpoint on commit.
--
Jacco Schalkwijk
SQL Server MVP
"Sanjay" <sanjayg@.hotmail.com> wrote in message
news:A1B8DE74-8DF1-4F7C-9341-3161D1F05158@.microsoft.com...
> Hi
> i have a question about what the COMMIT command actually does
> According to my understanding i thought a commit is just like including a
marker and it shouldnt take time to finish.
> Checkpoint is actuallly the process which writes committed transaction to
the disk so that should be the one taking time.
> If this is true why does BCP in take a long time at the end when its
commiting all rows copied from the file
> Anywhere i can go to read about what commit actually does and what
checkpoint does etc
> Sanjay
>|||If I am not mistaken, BCP can also defer all index fixups to once ( at the
end)... I think TABLOCK might be required for this, but i am not sure...
--
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Sanjay" <sanjayg@.hotmail.com> wrote in message
news:A1B8DE74-8DF1-4F7C-9341-3161D1F05158@.microsoft.com...
> Hi
> i have a question about what the COMMIT command actually does
> According to my understanding i thought a commit is just like including a
marker and it shouldnt take time to finish.
> Checkpoint is actuallly the process which writes committed transaction to
the disk so that should be the one taking time.
> If this is true why does BCP in take a long time at the end when its
commiting all rows copied from the file
> Anywhere i can go to read about what commit actually does and what
checkpoint does etc
> Sanjay
>|||I think what you are looking for is the batch size. If
you do not specify a batch size by using ther -b
parameter, the entire set of rows being inserted is
treated as one transaction and all row inserts are
commited and checkpointed at the same time.
This option is documented in the BOL.
I hope that this helps.
Matthew Bando
BandoM@.CSCTechnologies(remove).com
>--Original Message--
>Hi
>i have a question about what the COMMIT command actually
does
>According to my understanding i thought a commit is just
like including a marker and it shouldnt take time to
finish.
>Checkpoint is actuallly the process which writes
committed transaction to the disk so that should be the
one taking time.
>If this is true why does BCP in take a long time at the
end when its commiting all rows copied from the file
>Anywhere i can go to read about what commit actually
does and what checkpoint does etc
>Sanjay
>.
>

question on commit

Hi
i have a question about what the COMMIT command actually does
According to my understanding i thought a commit is just like including a ma
rker and it shouldnt take time to finish.
Checkpoint is actuallly the process which writes committed transaction to th
e disk so that should be the one taking time.
If this is true why does BCP in take a long time at the end when its commiti
ng all rows copied from the file
Anywhere i can go to read about what commit actually does and what checkpoin
t does etc
SanjaySanjay
BOL says:
COMMIT TRANSACTION
Marks the end of a successful implicit or user-defined transaction. If
@.@.TRANCOUNT is 1, COMMIT TRANSACTION makes all data modifications performed
since the start of the transaction a permanent part of the database, frees
the resources held by the connection, and decrements @.@.TRANCOUNT to 0. If
@.@.TRANCOUNT is greater than 1, COMMIT TRANSACTION decrements @.@.TRANCOUNT
only by 1.
"Sanjay" <sanjayg@.hotmail.com> wrote in message
news:A1B8DE74-8DF1-4F7C-9341-3161D1F05158@.microsoft.com...
quote:

> Hi
> i have a question about what the COMMIT command actually does
> According to my understanding i thought a commit is just like including a

marker and it shouldnt take time to finish.
quote:

> Checkpoint is actuallly the process which writes committed transaction to

the disk so that should be the one taking time.
quote:

> If this is true why does BCP in take a long time at the end when its

commiting all rows copied from the file
quote:

> Anywhere i can go to read about what commit actually does and what

checkpoint does etc
quote:

> Sanjay
>
|||Hi Sanjay,
By default checkpoints happen automatically and very regularly on SQL
Server. How often a checkpoint happen is determined by the Recovery Interval
setting. If SQL Server determines that the estimate time to recover the
database by rolling forward the transactions in the transaction log is
longer than the recovery interval, it will issue a checkpoint so all the
changes are flushed to the data file and don't have to be rolled forward the
next time the database starts up.
What I think happens is that BCP makes so many changes that it automatically
triggers a checkpoint on commit.
Jacco Schalkwijk
SQL Server MVP
"Sanjay" <sanjayg@.hotmail.com> wrote in message
news:A1B8DE74-8DF1-4F7C-9341-3161D1F05158@.microsoft.com...
quote:

> Hi
> i have a question about what the COMMIT command actually does
> According to my understanding i thought a commit is just like including a

marker and it shouldnt take time to finish.
quote:

> Checkpoint is actuallly the process which writes committed transaction to

the disk so that should be the one taking time.
quote:

> If this is true why does BCP in take a long time at the end when its

commiting all rows copied from the file
quote:

> Anywhere i can go to read about what commit actually does and what

checkpoint does etc
quote:

> Sanjay
>
|||If I am not mistaken, BCP can also defer all index fixups to once ( at the
end)... I think TABLOCK might be required for this, but i am not sure...
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Sanjay" <sanjayg@.hotmail.com> wrote in message
news:A1B8DE74-8DF1-4F7C-9341-3161D1F05158@.microsoft.com...
quote:

> Hi
> i have a question about what the COMMIT command actually does
> According to my understanding i thought a commit is just like including a

marker and it shouldnt take time to finish.
quote:

> Checkpoint is actuallly the process which writes committed transaction to

the disk so that should be the one taking time.
quote:

> If this is true why does BCP in take a long time at the end when its

commiting all rows copied from the file
quote:

> Anywhere i can go to read about what commit actually does and what

checkpoint does etc
quote:

> Sanjay
>