Forum Replies Created

Viewing 15 posts - 196 through 210 (of 1,353 total)

  • RE: Measure Calculation

    As it seems as if you're waiting for an answer, I'm not going to be able to look at this until the weekend.  I want to review one of my...

  • RE: Measure Calculation

    If that field is subject to modification, that might be a real problem.

    If that were true, it wouldn't be something he should be aggregating on.  I have...

  • RE: Measure Calculation

    Make sure you cluster on whatever field is aggregated.  Otherwise the engine will have to do table scans.

  • RE: Dealing with Disparate Goals

    Some of those issues reflect inertia and misplaced trust.  Both Truman and the UN wanted to reunite Korea per pre-war UN declarations.  But only if the Chinese wouldn't intervene.  Given MacArthur's...

  • RE: Dilemma between Microsoft BI developer or Application Developer

    I am stuck in a dilemma

    It's a small but not unimportant choice--a dilemma is a choice between undesirable alternatives.  You simply have a choice, as I have...

  • RE: Azure DWH part 28: The ASDW enemies

    Romac - Tuesday, June 26, 2018 4:49 AM

    Enemies?

    It's just a headline grabber.  He uses the more appropriate term "competitors" at the end...

  • RE: Measure Calculation

    iif(CoalesceEmpty([Measures].[Claim Paid Count],0) = 0
    , [Measures].[Reserve]
    ,[Measures].[Reserve] / [Measures].[Claim Paid Count])

    That's not particularly "kludgy", but since you are using 2014 you should be able...

  • RE: Measure Calculation

    Why can't one of the fact measure groups have a single contract as the granularity and the measures are the aggregations (whether count or sum)?

  • RE: Measure Calculation

    Distinct counts are tricky and generally if not universally require their own fact measure group in a cube.  Based on what you are saying, what immediately springs to my mind...

  • RE: Clustered PK perf -

    If there is a useable business key on the fact table, use it for the primary key, usually though without clustering it.  That's not always possible, but often the fact...

  • RE: Joining a large table to itself....better ideas?

    Nothing has changed my original view that each row is a trip with columns for pickup and drop off information. The drop off information is null until the...

  • RE: Joining a large table to itself....better ideas?

    I wouldn't use a view either.  I find no use for them in an OLTP environment.  There are a couple of situations where they are useful.  I just haven't had...

  • RE: Joining a large table to itself....better ideas?

    Although there is some good merit in a guaranteed "only 2 values" (pickup/dropoff) type of table, a proper CROSSTAB would likely blow the doors off of any view you...

  • RE: Joining a large table to itself....better ideas?

    You also may want to consider reworking the table if possible.  If a completed trip consists of both a pickup and a drop off, they could be the same record. ...

  • RE: SQL Server 2016 SP2 Issue with Analysis Services

    Applying CU1 to SP2 resolved the issues we were having.  If you use SSAS and apply SP2, you should plan to apply CU1 as well.

Viewing 15 posts - 196 through 210 (of 1,353 total)