When you create a named set in AS, it seems to be a flat set and drilldown or drillup is not possible. How can I implement something like a named set that would allow drilldown?
View Complete Post
I'm trying to build some requested relative date logic in a SSAS 2005 cube. I can build the named sets, and they work fine. When I drag them out as a column in my tool (Cognos, if it's relevant) it lists the actual members of the named set.
I would like to give those members some sort of artificial parent, so that when I add it, I get the parent. If I drill into it, I get the actual members.
Hopefully this makes sense. I'm very new to SSAS, so I may be messing up my terminology.
I’m going to describe our SSAS solution a bit and what I have in it so far in order to ask the question regarding “year-to-date” sales. This is part example and part question, I suppose. "The Filter Field Conundrum" sounds like
it should be a high-tech Encyclopedia Brown case or something. Can't seem to find a similar situation through searching, although perhaps I'm wrong and this has been done before.
We have a data warehouse that contains our transactional detail for the last nine or so years. Tables are somewhat analogous to the AdventureWorks solution, with a table for Sales, a table for Customers, Geographic information, etc. The data
warehouse has a time table that contains many of the usual bits of information one would expect:
Full Date (mm/dd/yyyy)
Day of Month
Day of Week
Day of Week Name
Day of Year
Week of Year
and maybe a few other typical fields.
Then we also have:
Working Day (bit, with a 1 indicating that this was a scheduled working day according to our company calendar, and a 0 indicating that it was not)
Working Day of Month
Working Day of Year
(these fields indicate that a day is the nth scheduled working day, according to our company calendar, for a given month or year)
So, for example, 5/1
I have a simple cube deployed and I just now added a named set using the TopCount functin as follows:
After processing, I can see and use the new Named Set in both the BIDS Cube Browser and in Excel, but another user cannot even see it. I have Administrator rights on the Analysis Server, he is simpl
I have some Named Sets that I want to translate. I have done exactly the same way as with the Calculated Members but the Sets don´t use the translations? Any ide why?
MSDN Magazine October 2003
MSDN Magazine July 2003
My webpage has one banner with a logo, a vertical menu bar on the left side of the page and a footer . I have 5 other pages which should get loaded when the user select them from the menu bar. what my concern is actually the banner, menu bar and the footer should not change when the requested page loads. This definitely can be handled by sets. But I want to know whether there are any other alternatives for frame sets or could master page be helpful for this purpose ?????
Any help would be appreciative .
I have a stored proc that returns 4 resultsets, they are in the format.
ALTER PROCEDURE [dbo].[pGetManagerEmployeeSummaryDummy] @ManagerStaffID int, @PeriodID intASSET NOCOUNT ON;SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED;IF EXISTS (select 1 from dbo.temployee e inner join dbo.temployeedetail ed on e.staffindividualid = ed.staffindividualid and ed.periodid = @PeriodID inner join Incentive.tRole r on rm.IncentiveRoleID = r.RoleID where ed.ManagerIndividualStaffID = @ManagerStaffID AND r.RoleID = 1) --CloserBEGIN SELECT e.StaffIndividualID, e.LastName, e.FirstName, r.RoleName, e.xname, e.yname
from dbo.temployee e
inner join dbo.temployeedetail ed on e.staffindividualid = ed.staffindividualid and ed.periodid = @PeriodID
where ed.ManagerIndividualStaffID = @ManagerStaffID a
Search server gatherer calls CloseAccessor() and shutdown() on ISearchProtocol after GetChunk() even if the FILTER_E_END_OF_CHUNKS is not returned. After calling shutdown() it stops calling the createaccessor() with new URL. I want to create a hierarchical
indexing but I am not gatherer is not suporting this. The same piece of code is working fine in MOSS 2007, I am facing this issue in MOSS 2010 only. Is there anything changed in MOSS 2010 which is creating this issue?