named transaction

Hi,
I need to make sure i do not open second transaction if one is already
opened,
i wanted to name a transaction, but how can i cjeck if a transaction with
that name is already open?
mndreu
On Mon, 7 Feb 2005 09:20:43 +0100, Malgorzata Ndreu wrote:

>Hi,
>I need to make sure i do not open second transaction if one is already
>opened,
Hi mndreu,
Check @.@.TRANCOUNT.

>i wanted to name a transaction, but how can i cjeck if a transaction with
>that name is already open?
If @.@.TRANCOUNT is 0, no transaction at all is open.
If @.@.TRANCOUNT is > 0, I know of no way to check if the open transactions
are named and what their names are.
Best, Hugo
(Remove _NO_ and _SPAM_ to get my e-mail address)

Named subscription is greyed out

The system consists of one SQL 2000 Server (Distributor and Publisher) and
several subscribers running MSDE 2000 and Merge Replication. Every
Subscriber connects to the publisher using Pull Subscription, but the choice
of selecting "No, This is a named subscription" is grayed out when
establishing the subscription. I therefore have to pick Anonymous
subscription... Why?
You'll need to register the subscribers first.
With the MSDE subscriber connected to your publisher, in Enterprise Mgr:
right click Replication and select the Config. Publishers, Subscriber and
Distributors option. On the Subscribers tab, select the box next to the
Subscribers to register them. Enter the connecting account using the ...
button. Then re-create the pull subscription.
Had the same problem myself recently.
Steve Halfacre
Synapsis, UK
<hallvardsc@.hotmail.com> wrote in message
news:%23dPPwIeLEHA.340@.TK2MSFTNGP11.phx.gbl...
> The system consists of one SQL 2000 Server (Distributor and Publisher) and
> several subscribers running MSDE 2000 and Merge Replication. Every
> Subscriber connects to the publisher using Pull Subscription, but the
choice
> of selecting "No, This is a named subscription" is grayed out when
> establishing the subscription. I therefore have to pick Anonymous
> subscription... Why?
>
>
sql

Named sets and Existing

I have a very large Account dimension (> 2,000,000 members). I would like to create a named set for the top most profitable accounts. I plan to use this named set in the SSRS Report Builder to compensate for its lack of aTop N feature. The problem is that the user can change the fiscal period and SSAS needs to reevaluate the set. Using Generate function won't work for performance reasons. So, I'm trying to use Existing to force the set generation. e.g.

CREATE SET CURRENTCUBE.[Top 5 Profitable Accounts]

AS

Order(TopCount(

(EXISTING [Account].[Account].[Account].Members, [Period].[Period].CurrentMember), 5, [Measures].[Profit]),

[Measures].[Profit], DESC);

However, this gives me "The Period hierarchy already appears in the Axis1 axis." error when I test the set with the following query

select non empty [Measures].[Profit] on 0,

non empty [Top 5 Profitable Accounts] on 1

from [RPM]

WHERE [Period].[Period].&[20030228]

and duplicated dimensionality error in the Report Builder.

Does anyone know how this could be implemented?

There are a couple of issues in the Named Set:

The error can be eliminated by not explicitly specifying [Period].[Period].CurrentMember with Existing.|||

Deepak,

Thank you for helping. True, the modified set doesn't error out. However, as you pointed out, it is not dynamic. It only works with the default time period which is where I started. In other words, EXISTING doesn't help here. Changing the query slicer to a different time period doesn't produce any results. It looks like we cannot change the context of standard named sets defined with CREATE SET in the cube script. This pretty much leaves me with no options to simulate TopN with the Report Builder.

Named Sets

Hi,

I defined 2 Named Sets, so as to filter my calculated members:

NamedSet1:

{([Dimension1].[MyLevel1].&[X]),([Dimension1].[MyLevel1].&[Y']),([Dimension1].[MyLevel1].&[Z'])}

NamedSet2:

{([Dimension2].[MyLevel2].&[A']),([Dimension2].[MyLevel2].&[B']),([Dimension2].[MyLevel2].&[C'])}

It works well, but I didn't manage to use them in the same expression like

Sum(Crossjoin([NamedSet1],[NamedSet2], [Measures].[TurnOver]), the result is wrong.

Does anybody know how to do that ?

Regards

Ayzan

I wrote a short sample for you that works with Adventure Works. If this doesn't help, please, explain your scenario better, especially your calculations, expected result and actual result.

with
set set1 as '{ [Product].[Category].&[1], [Product].[Category].&[3] }'
set set2 as '{[Product].[Color].&[Black], [Product].[Color].&[White]}'
member x as 'sum(crossjoin(set1,set2), measures.[Customer Count])'
select x on 0 from [Adventure Works]

NAMED SET/ CALCULATED FIELDS

Hi,

Can I use the following MDX in named set/ calculated fields:

with member [MEASURES].[thisistheratio] as

([Direction].[Direction].&[1],[Measures].[Activity Count])/

([Direction].[Direction].[ALL],[Measures].[Activity Count]),

FORMAT="0%"

Select {[Measures].[Activity Count],

[MEASURES].[thisistheratio]} on columns,

{[Direction].[Direction].mEMBERS} on rows

FROM [CASEACTIVITYDETAIL]

how do I use it? Is there a particular syntax if you apply it inside named sets/calculated fields?

thanks a lot!

cherriesh wrote:

Hi,

Can I use the following MDX in named set/ calculated fields:

with member [MEASURES].[thisistheratio] as

([Direction].[Direction].&[1],[Measures].[Activity Count])/

([Direction].[Direction].[ALL],[Measures].[Activity Count]),

FORMAT="0%"

Select {[Measures].[Activity Count],

[MEASURES].[thisistheratio]} on columns,

{[Direction].[Direction].mEMBERS} on rows

FROM [CASEACTIVITYDETAIL]

how do I use it? Is there a particular syntax if you apply it inside named sets/calculated fields?

thanks a lot!

What you have there is an MDX query, you cannot put the whole thing inside a calculated member/set. I am guessing that what you probably want to do is to create a calculated measure for this ratio. If this is the case you could do either of the following.

If you open up your cube and click on the calculations tab, about the 4th button along the top will be an "New Calculated Member" button. When you click on this it brings up a form to let you add a new calculated member and you would fill out the following properties:

Name: [thisistheratio]

Parent Hierarchy: MEASURES

Expression:

([Direction].[Direction].&[1],[Measures].[Activity Count])/

([Direction].[Direction].[ALL],[Measures].[Activity Count])

Format String: "0%"

Alternatively you could switch to the script view and just paste in:

CREATE MEMBER CURRENTCUBE.Measure.[thisistheratio]

AS

([Direction].[Direction].&[1],[Measures].[Activity Count])/

([Direction].[Direction].[ALL],[Measures].[Activity Count]),

FORMAT="0%";

Named Set with TOPCOUNT Not Working Correctly

I need to create reports that contain our top 15 customers at any given point in time. I created the following Named Set using the TopCount function in SSAS 2005:

TOPCOUNT([Customer].[Customer Type-Name-Door Hierarchy].[Customer Name].members, 15, [Measures].[Net Ship Dollars])

When I bring this set into the client (Excel 2007 pivot table), its shows our top 15 customers for all time. When I add a date filter for just 2007, it doesn't update the list to just show the top customers for 2007. It just keeps the same "all time" group.

When I create this named set in a browser query, it works correctly. That is, it shows the top 15 customers for 2007. Is there any way I can get the Named Set created in SSAS to show the correct data based on the filtered date in the client?

Here is the browser query:

WITHSET

[Top Performers]

AS

'TOPCOUNT([Customer].[Customer Type-Name-Door Hierarchy].[Customer Name].members, 15, [Measures].[Net Ship Dollars])'

SELECT

{[Measures].[Net Ship Dollars]} ONCOLUMNS,

{[Top Performers]}ONROWS

FROM Shipments

Where ([Date].[Calendar Year].&[2007])

Thank you.

David

Are you using AS 2005 SP2? This problem has been fixed there.|||

The problem here is because the named set in the MDX Script gets resolved when it is first parsed at which time all the other dimensions will be set to their default members (which is usually the "All" member). Using the EXISTING statement in your set definition should force it to be re-evaluated with the current context each time it is used.

eg

TOPCOUNT(EXISTING [Customer].[Customer Type-Name-Door Hierarchy].[Customer Name].members, 15, [Measures].[Net Ship Dollars])

|||I am using SP2 but still experiencing the problem.|||

Darren,

I tried this but the same problem is occuring. Apparently, the default member of the time hierarchy determines what customer members to return. When I changed the default member to 2007, the named set showed the top customers for 2007. I came across another post which confirmed this as a problem. Does anybody have any workarounds? Thyank you.

David

|||

Hi David,

It seems that I did not read your full question and missed some information. So, just want to clarify. Named sets in AS 2005 are static named sets, which means that they are calculated just once in the context of the current member awailable at that moment. They are not reevaluated during execution of the select statement. Daren is right in the fact that named sets created in the cube scope or session scope (using Create statement) are evaluated when the CREATE statement is executed, therefore TopCount is calculated in the context of the default member. Sets created in the query scope using With clause are evaluated right after the WHERE clause and therefore take current member defined by the where clause in concideration (this is why your query with WITH statement works as you expect and query with named set from CREATE statement return different results). There are it's own pros on having static named sets (mostly performance), but in your case you should try to avoid using TopCount in the named set, if you want the members on other axis to affect results of the topcount.

Irina

P.S.

>>> I came across another post which confirmed this as a problem.

Could you please point me to this thread?

|||

Irina Gorbach wrote:

Named sets in AS 2005 are static named sets, which means that they are calculated just once in the context of the current member awailable at that moment. They are not reevaluated during execution of the select statement.

Of course! sorry for leading you slightly astray. The EXISTING statement will work if you have a set in a calculation

eg

CREATE MEMBER CurrentCube.Measures.CustomersInTop10Pcnt AS COUNT(TOPPERCENT(EXISTING Customer.Customer.Members, 150 Measures.Sales)

This would re-evaluate the set used in the toppercent function based on the current slicing conditions, which is similar, but different.

|||so is this the solution then?

TOPCOUNT(EXISTING [Customer].[Customer Type-Name-Door Hierarchy].[Customer Name].members, 15, [Measures].[Net Ship Dollars])

or is there another way?

Also, how do you get it to sort correctly in excel, if you pull over the named set it just shows you the top X sorted by the SET Expression, whereas if you do an MDX query it sorts it by the Numeric Expression

Named Set with TOPCOUNT Not Working Correctly

I need to create reports that contain our top 15 customers at any given point in time. I created the following Named Set using the TopCount function in SSAS 2005:

TOPCOUNT([Customer].[Customer Type-Name-Door Hierarchy].[Customer Name].members, 15, [Measures].[Net Ship Dollars])

When I bring this set into the client (Excel 2007 pivot table), its shows our top 15 customers for all time. When I add a date filter for just 2007, it doesn't update the list to just show the top customers for 2007. It just keeps the same "all time" group.

When I create this named set in a browser query, it works correctly. That is, it shows the top 15 customers for 2007. Is there any way I can get the Named Set created in SSAS to show the correct data based on the filtered date in the client?

Here is the browser query:

WITH SET

[Top Performers]

AS

'TOPCOUNT([Customer].[Customer Type-Name-Door Hierarchy].[Customer Name].members, 15, [Measures].[Net Ship Dollars])'

SELECT

{[Measures].[Net Ship Dollars]} ON COLUMNS,

{[Top Performers]}ON ROWS

FROM Shipments

Where ([Date].[Calendar Year].&[2007])

Thank you.

David

Are you using AS 2005 SP2? This problem has been fixed there.|||

The problem here is because the named set in the MDX Script gets resolved when it is first parsed at which time all the other dimensions will be set to their default members (which is usually the "All" member). Using the EXISTING statement in your set definition should force it to be re-evaluated with the current context each time it is used.

eg

TOPCOUNT(EXISTING [Customer].[Customer Type-Name-Door Hierarchy].[Customer Name].members, 15, [Measures].[Net Ship Dollars])

|||I am using SP2 but still experiencing the problem.|||

Darren,

I tried this but the same problem is occuring. Apparently, the default member of the time hierarchy determines what customer members to return. When I changed the default member to 2007, the named set showed the top customers for 2007. I came across another post which confirmed this as a problem. Does anybody have any workarounds? Thyank you.

David

|||

Hi David,

It seems that I did not read your full question and missed some information. So, just want to clarify. Named sets in AS 2005 are static named sets, which means that they are calculated just once in the context of the current member awailable at that moment. They are not reevaluated during execution of the select statement. Daren is right in the fact that named sets created in the cube scope or session scope (using Create statement) are evaluated when the CREATE statement is executed, therefore TopCount is calculated in the context of the default member. Sets created in the query scope using With clause are evaluated right after the WHERE clause and therefore take current member defined by the where clause in concideration (this is why your query with WITH statement works as you expect and query with named set from CREATE statement return different results). There are it's own pros on having static named sets (mostly performance), but in your case you should try to avoid using TopCount in the named set, if you want the members on other axis to affect results of the topcount.

Irina

P.S.

>>> I came across another post which confirmed this as a problem.

Could you please point me to this thread?

|||

Irina Gorbach wrote:

Named sets in AS 2005 are static named sets, which means that they are calculated just once in the context of the current member awailable at that moment. They are not reevaluated during execution of the select statement.

Of course! sorry for leading you slightly astray. The EXISTING statement will work if you have a set in a calculation

eg

CREATE MEMBER CurrentCube.Measures.CustomersInTop10Pcnt AS COUNT(TOPPERCENT(EXISTING Customer.Customer.Members, 150 Measures.Sales)

This would re-evaluate the set used in the toppercent function based on the current slicing conditions, which is similar, but different.

|||so is this the solution then?

TOPCOUNT(EXISTING [Customer].[Customer Type-Name-Door Hierarchy].[Customer Name].members, 15, [Measures].[Net Ship Dollars])

or is there another way?

Also, how do you get it to sort correctly in excel, if you pull over the named set it just shows you the top X sorted by the SET Expression, whereas if you do an MDX query it sorts it by the Numeric Expression
sql

named set with a condition

I am having a little problem with returning 13 or 14 periods in a named set. Is it possible to have a condition in a named set

ie if there is not a string of "14" in the set of (last 13 periods) then return the set of 13 periods else return the set of 14 periods.

Thanks.
Mark.

Hi Mark,

generally named sets are static and will be computed ones in the scope they belong to.

Could you please provide your sample set expression and query that used it?

Best regards,

Vladimir

|||

Code Snippet

{LastPeriods(12,Filter([Accounting Week Calendar].[Accounting Period].Members, [Accounting Week Calendar].Currentmember.Properties("Current Period")<>"0").Item(0))}

This provides me with a set of 12 periods.

What I want is to return preferably as a named is a set of 13 or 14 periods. This is to give a Moving annual total. We will return 13 periods if all of the periods contain 4 weeks, we will return 14 periods if they dont. We know that it if there is a period 14 it will only ever contain 1 week.

Need some way to provide this from the cube rather than the users doing the arithmetic.

As a blunt method I could use an iif insode a named set if this is possible.

Thanks.
Mark.

Named set using LastPeriods (but not all of them)

To get the current period we have a named set Current Period. To get the last 13 periods we have a named set Last 13 Periods. We can aslo detect period that are not period 14.

Period 14 is an oddball period and I want to skip over it i.e Last 12 Periods will aways show data for the previuous 12 periods that were not periods 14s.

How do we link all of this to give the last 13 periods which were not a period 14?

Many thanks this is driving me bonkers.
Mark.

Code Snippet

CURRENT PERIOD
{
Filter([Alt Week Calendar].[Accounting Period].Members, [Alt Week Calendar].Currentmember.Properties("Period14")="1")
}

LAST 13 PERIODS
{LastPeriods
(13,Filter([Alt Week Calendar].[Accounting Period].Members,[Alt Week Calendar].Currentmember.Properties("Current Period")<>"0").Item(0))
}

NOT PERIOD 14
{
Filter([Alt Week Calendar].[Accounting Period].Members,[Accounting Week Calendar].Currentmember.Properties("Period14")<>"1")
}

Hi Mark,

Here's an example from Adventure Works which returns the last three days that aren't weekends:

Code Snippet

with member measures.demo as

generate(

tail(

exists(

[Date].[Date].currentmember.lag(5):[Date].[Date].currentmember

, [Date].[Day Name].&[2]:[Date].[Day Name].&[6])

,3)

, [Date].[Date].currentmember.name + " (" + [Date].[Date].currentmember.properties("Day Name") + ")", ", ")

select measures.demo on 0,

[Date].[Date].[Date].members on 1

from [Adventure Works]

What I'm doing here is finding the last five days, using an exists to get only the days from that set which are weekdays, then finding the last three days in the resulting set. The outermost Generate() is simply there to display the results of the expression in an easy-to-read way.

HTH,

Chris

named set questions

As I understand it, a named set is not processed until it is needed.

Once these are processed are they cached for use by other client requests?

If there are Aggregations set up in the cube will this trigger the named sets be processed right away with the cube?

I assume that if a named set is too big there could be loss in performance, is there a way to hold down the size of a named set?

here are some examples of named sets i've created using some calculated members. perhaps there is a better way of doing this?

*************** Calculated Members***************************

CREATE MEMBER CURRENTCUBE.[MEASURES].[HP Plus Addl Billing]

AS aggregate([PREP CONTROL HDR].[Bill Formats].&[19],[Measures].[Billed Sales Amount]),

FORMAT_STRING = "Currency",

VISIBLE = 1;

2nd calculated member

CREATE MEMBER CURRENTCUBE.[MEASURES].[Prep Billing]

AS AGGREGATE(EXCEPT([PREP CONTROL HDR].[Bill Formats].[Bill Formats] ,{[PREP CONTROL HDR].[Bill Formats].&[19],[PREP CONTROL HDR].[Bill Formats].&[7]}),[Measures].[Billed Sales Amount]),

FORMAT_STRING = "Currency",

VISIBLE = 1;

*******************named sets************************************

CREATE SET CURRENTCUBE.[CTP Customers]

AS FILTER([CUSTOMER JOB].[Title Name].[Title Name].members,([Job Complete Date].[Calendar Full],[Measures].[HP Plus Addl Billing])> 0 );

CREATE SET CURRENTCUBE.[Prep Customers]

AS FILTER([CUSTOMER JOB].[Title Name].[Title Name].members,([Job Complete Date].[Year].&[2005],[Measures].[Prep Billing]) > 5000 ) ;

This one, I've used other named sets to create another named set.

Is this a bad thing?

CREATE SET CURRENTCUBE.[Non-Prep-Photo Customers]

AS EXCEPT([CTP Customers],{[Prep Customers],[Photo Customers]});

As I understand it, a named set is not processed until it is needed.

Once these are processed are they cached for use by other client requests?

Actually no - named sets are always processed and evaluated during MDX Script execution. This is done once, and they are cached afterwards.

|||

We've had issues where after the cube was processed it was not available for running reports until the server was rebooted.

When we removed the named sets the issue went away.

Is there any issues related to using named sets on a 32bit server running sql server 2005?

Named Set Question

I want to create a named set that includes a list of some of our major customers. As part of the set, I also want to add a calculated member that represents a subtotal of customers. For example:

{[Customer].[Customer Hierarchy].[Store].&[Smith Stores],[Customer].[Customer Hierarchy].[Store].&[Williams Stores],[Customer].[Customer Hierarchy].[Store].&[Lion Stores]}

represents a named set of three customers. In the named set, I want to add Smith Stores and Williams Stores together to create a subtotal called Midwest Group. So, my revised set would look like:

{[Customer].[Customer Hierarchy].[Store].&[Smith Stores],[Customer].[Customer Hierarchy].[Store].&[Williams Stores],[Customer].[Customer Hierarchy].[Store].&[Lion Stores], [Customer].[Customer Hierarchy].[Store].&[Midwest Group]}.

First, can I create a calculation such as [Customer].[Customer Hierarchy].[Store].&[Smith Stores] + [Customer].[Customer Hierarchy].[Store].&[Williams Stores] AS 'Midwest Group' and add it directly to the named set. Or can I create this as a calculated member and add this member to the named set.

Is what I would like to do possible with named sets?

Thank you.

David

You will have to first create calculated member and then add it to the set. Alternative approach is to add new attribute to the Customer dimension with members Major/Minor. This way you will be able to get your Major customer by slicing on that attribute. You also will be able to do any grouping you want. This is more scalable approach once your company grows and you have more than 3 major customers |||

Mosha, when adding the calculated member to the named set, are there any restrictions. For example, does the calculated member need to be in the same hierarchy as the other members of the set. Also, are there any syntax differences when adding the calculated member. For example, is it treated like any other tuple and I would just separate it from the other members with a comma? Thank you.

David

|||There are no special restrictions. The calculated member will have to be from the same hierarchy as other members, but this is not special requirements for the calculated members, all tuples in the set must have same dimensionality (hierarchility). Syntax is the same - if you enumerate the members, than use comma as separator.|||

Mosha, Thank you for the answer. One problem remains. I get the named set working correctly when I run an MDX query in Management Studio. I have the named set appearing in the row axis and everything displays correctly. When I use the same named set in an Excel 2007 pivot table, I get an error message -- "A set has been encountered that cannot contain calculated members". I do have "show calculated members from OLAP Server" box checked in Pivot Table Options in Excel. Is this a bug with Excel 2007?

David

|||I am not sure what exactly you do in Excel - but it is possible that it is limitation of either Excel or AS (the error message is actually from AS, not from Excel).|||

Mosha,

Is it unusual that an MDX query would work correctly in SQL Server Management Studio but yield an error in a front end client?

David

|||Well, obviously the query that you wrote in Management Studio and the query that Excel generated are different queries.

Named set is not working in excel

Hi All,

I have created the named set to get the top 4 referers for my products.

But it is not working as expected.I am using Ecel 2007 as reporting UI using Pivot tables.

The referers are in rows and product is in filter.

Say I want the top referers (google.com,altavista.com...etc) for VB (or) VC++ or SQL 2005 ....etc

Please suggest me how I can do this i.e arrange in order and vary with change of product.

I have three tables Dim_Product, Dim_Referer, Fact table

The content of this new named set would be:

{([Dim Referer].[name category].Members,4,[Measures].[value])}

Rgds

Sai

Named sets created in the MDX Script are static - they are evaluated only once. Therefore changing the current product won't affect the content of the named set.sql

Named Set in Excel Pivot Table Displays as Enumeration

Pardon me if this is really an Excel 2007 Pivot table question. I have a named set defined in the cube as:

CREATE SET CURRENTCUBE. [Team Building Overall]

AS {[Question].[Short Name].[Q-02],

[Question].[Short Name].[Q-03],

[Question].[Short Name].[Q-05],

[Question].[Short Name].[Q-06],

[Question].[Short Name].[Q-08],

[Question].[Short Name].[Q-13],

[Question].[Short Name].[Q-17],

[Question].[Short Name].[Q-18],

[Question].[Short Name].[Q-21],

[Question].[Short Name].[Q-30],

[Question].[Short Name].[Q-31]};

And can display measure values for this set as whole in Proclarity with:

SELECT { [Measures].[Average]} ON COLUMNS ,

{ [Corporate Hierarchy].[Hierarchy].DEFAULTMEMBER } ON ROWS

FROM [360 Training Survey]

WHERE ([Team Building Overall], [Test Month].[Test Month].&[200704] )

CELL PROPERTIES VALUE, FORMATTED_VALUE, CELL_ORDINAL, ACTION_TYPE

In Excel 2007, unfortunately I can not use this set as a filter as I can in Proclarity. Rather, the best I can accomplish is to display this as 11 different columns, one for each member of this named set.

Any suggestions ?

Anyone ?

I figure I can create a calculated measure in the cube named [Team Building Overall Average] which is defined as ([Team Building Overall],[measures].[Average]), but this seems a bit klutzy, especially given that I have eight sets and six measures, thus resulting in a total of 48 calculate measures I need to create.

|||

You could create a measure independant calculated member in the Question dimension as follows.

CREATE MEMBER CurrentCube.[Question].[Short Name].[Team Building Overall] AS AGGREGATE([Team Building Overall])

If the only reason that you have the sets is for filtering you could put the set definition inline in this memeber, otherwise you could leave them separate.

NAMED SET / PIVOT TABLE ! HELP ME

NEED KNOW IF SOMETHING KNOW CERTANLY ....ABOUT THIS :

************************************************** ********************************
PLACE A NAMED SET INTO A PIVOT TABLE : ALL ABOUT THIS..FORMULAS...FORMS...
EXAMPLES... ALL !

ANOTHER : GET RELATIONSHIP ABOUT THE FIRST TROUBLE : SEE A NAMED SET FROM A
CUBE ( OLAP)

************************************************** ************************************************

REALLY NEED ALL ABOUT YOU CAN SEND ME.AND WRITE ME ...A OLNLY FIN MANY
QUESTIONS IN FORUMS...BUT NO ONE RESPONSES....APARENTLY TOO MUCH PEOPLE
HAVE THIS TROUBLE ..... I KNOW ...NO EVERY DAY .MEMBERS THAT POST IN THIS
WEBSITE..TAKE REPLY...BUT......, REALLY NEED INFO ABOUT .AS SOON AS
POSSIBLE...
MI E-MAIL :
THANABULLET@.HOTMAIL.COM

THANKS !.
MY BEST WISHES...

--
hi all !wow

it shows up just like a dimension i thought

are you using the olap 8.0 oledb provider?

-aaron
msolap1.1 or somethign right

named server failed logon after installing MS04-011 patch

Need help urgently.
I have on win 2000 machine a default SQL Server (local) & a named SQL Server
instance (for separate web machine).
After installing the MS04-011 Patch last nite, the named SQL Server fails to
startup on reboot or manual. The default server on the other hand is runnin
g. But I cannot use the default server as it requires access within the loca
l machine only.
I tried uninstalling the patch, but it still cannot get the SQL server runni
ng again.
HOW CAN I RECOVER THE SQL Server Instance?
Additional info: On logon, following error massage:
"NtUninstall Q8877565\WinSys.cer" not found
before and after the uninstall of the patch.What error do you get when you start it? Is there anything in he SQL Server
errorlog when it fails?
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Thank Rand for responding.
The Error is simply Login Failed. Service Manager shows the instance is stop
ped, while the Default Instance (Local) is started. Click start, and return
Login Failure again.
Any idea what's wrong and how I may recover the Instance?
Almon|||Error listing end at the last restart after patch install. That is, never re
start again.
Almon

named server failed logon after installing MS04-011 patch

Need help urgently
I have on win 2000 machine a default SQL Server (local) & a named SQL Server instance (for separate web machine)
After installing the MS04-011 Patch last nite, the named SQL Server fails to startup on reboot or manual. The default server on the other hand is running. But I cannot use the default server as it requires access within the local machine only
I tried uninstalling the patch, but it still cannot get the SQL server running again.
HOW CAN I RECOVER THE SQL Server Instance'
Additional info: On logon, following error massage
"NtUninstall Q8877565\WinSys.cer" not foun
before and after the uninstall of the patch.What error do you get when you start it? Is there anything in he SQL Server
errorlog when it fails?
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Thank Rand for responding
The Error is simply Login Failed. Service Manager shows the instance is stopped, while the Default Instance (Local) is started. Click start, and return Login Failure again
Any idea what's wrong and how I may recover the Instance
Almo|||Error listing end at the last restart after patch install. That is, never restart again
Almo

named server failed logon after installing MS04-011 patch

Need help urgently.
I have on win 2000 machine a default SQL Server (local) & a named SQL Server instance (for separate web machine).
After installing the MS04-011 Patch last nite, the named SQL Server fails to startup on reboot or manual. The default server on the other hand is running. But I cannot use the default server as it requires access within the local machine only.
I tried uninstalling the patch, but it still cannot get the SQL server running again.
HOW CAN I RECOVER THE SQL Server Instance?
Additional info: On logon, following error massage:
"NtUninstall Q8877565\WinSys.cer" not found
before and after the uninstall of the patch.
What error do you get when you start it? Is there anything in he SQL Server
errorlog when it fails?
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||Thank Rand for responding.
The Error is simply Login Failed. Service Manager shows the instance is stopped, while the Default Instance (Local) is started. Click start, and return Login Failure again.
Any idea what's wrong and how I may recover the Instance?
Almon
|||Error listing end at the last restart after patch install. That is, never restart again.
Almon
sql

Named Query on tables in separate dbs?

Is it possible to write a named query on tables in different databases?Sure, just use your standard TSQL syntax..

Select
A.field1,B.field2
from DB1.user.tablename A inner join DB2.user.tablename B
on A.ID = B.ID

C|||Actually I do not want to hard code the database name in the query. Can I use the datasources somehow?|||I have not been able to query across datasources.

If you just want to query one db, then you could create a view in one db that queries both dbs.

Named query not appearing in report builder

I'm having a heck of a time with named queries. At this point I just want a proof of concept in my DSV. I have a bunch of tables added to the DSV, and I would like to add a named query to it so the user can pick from the name query in report builder. What has to be done to make it appear in the report builder?

Nevermind. I didn't realize that the report model definition had to be refreshed.

Named query as a pivot

Hello,

Is it possible to create a named query in the DSV that is the result of a pivot (e.g. cross tab?). The number of columns as a result of the pivot are based the number of records in one of the driving tables - in other words, it is not fixed.

You got to go dynamic SQL and use some fancy report datasets and expressions to display or not the columns.

Then you would have to create a report were you define as many columns as possible and control the visibility of these columns based on some expression stored in the Column Visibity hidden property.

Lot of work. May be you would be better off sourcing your report out of a cube.

Philippe