Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 434
  • Last Modified:

Can I configure multiple surrogate keys on a table?

I am working with a Time table and time intelligence in ssas 2008. I would like to assign  surrogate keys to FIscal Year Fiscal Quarter Fiscal Month Fiscal Day.  

Is there a way to perform this in column properties in the current table?
0
rhservan
Asked:
rhservan
  • 4
  • 4
  • 2
2 Solutions
 
dqmqCommented:
I think you are misusing the term "surrogate keys".  "Surrogate keys" are assigned to tables, not to columns (FWIW, you can have as many as you want.  But what would be the point???) Also, surrogate keys are unique--if Fiscal Year were a surrogate key, then each year could only appear once in your table.  

Perhaps, do you mean "foreign key".  Not sure what you are trying to do?  

Or are you referring to the identity property?  Only one "identity" column is allowed per table.  

0
 
marappanCommented:
Hi rhservan,

                      I can help you with this. But, I need to know why do you want to use surrogate key instead of using natural key. If you have already chosen a primary key can i know what is that? Also can you please explain what you are going to achieve by adding surrogate key?

Thanks,
Marappan
0
 
marappanCommented:
If you are tying to enforce uniqueness to those four columns below is the syntax:

CREATE TABLE Calendar_DEMO
(
FIscal_Year INT NOT NULL UNIQUE,
Fiscal_Quarter INT NOT NULL UNIQUE,
Fiscal_Month INT NOT NULL UNIQUE,
Fiscal_Day INT NOT NULL UNIQUE
)
GO
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
rhservanAuthor Commented:
I am building Fiscal YTD, QTD, MTD & DTD.  It was suggested that I use surrogate keys in order to utilize a cumulative total for each period.
0
 
marappanCommented:
Can you please paste your scheme for better understanding?
0
 
rhservanAuthor Commented:
Schema attached.
SCHEMA.JPG
0
 
marappanCommented:
Can you please give me the name of the table and column name you want to implement the key?
0
 
rhservanAuthor Commented:
DimTimeIn
Fiscal YTD, QTD, MTD & DTD
0
 
rhservanAuthor Commented:
I am preparing to run the time intelligence tool on my cube.

The DimTimeIn Table was created with two calendars:
1. Calendar Year
2. Fiscal Year

I have built hierarchies in SSAS for Fiscal Year. I would like for this calendar to provide:
1.F Year To Date - When clicked on the year value It gives me a cumulative total from January 1
2. F Quarter To Date - When clicked on the quarter value it gives me cumulative total from the first day of that quarter.
etc......

Hope this helps  
0
 
dqmqCommented:
Let me comment on you DimTimeIn table.

1. It appears that it would be better named DimDate as the granularity is date, not time.  :>)

2. The table already has a surrogate key:  Date_Key.  To my way of thinking, PK_Date is also a surrogate key.  I'm still not quite "getting" the rationale for two surrogate keys on the same table.

3. The columns are present to do the rollups you desire.  I think what you are asking is there a way to combine the multi-column rollups into single-column rollups (for sake of simplicity, I guess).   Sure, you can do that.  

Let's say your FY column contains the 4-digit year and your FQ column contains the 1 digit quarter and your FM column contains the 1-2 digit month.  To do a rollup by month, you need to involve all 3 columns.  You can derive single columns: yyyyqq and yyyymm to enable single column rollups for FQ and FM.   You can even do it in a view or computed columns so that there is no effort to populate them and no chance they will get out of sync.  

4. Stiill not sure how "surrogate keys" apply to your situation.  The only "stretch" that comes to mind is if you are considering moving from a star design to a snowflake design. In that case FY, FQ, FM are dimensions in their own right and THOSE dim tables would best have surrogate keys that are referenced by foreign keys in the dimTimeIn table.

5.  I suppose I've confused you beyond hope, by now, so let me give the simple advice. Don't add anymore surrogate keys to dimTimeIn.  Do not add more foreign keys to the dimTimeIn table.  Either derive the new columns you need or if you need add FQ, FY dimensions and link them to your fact table.

 







 


 

0

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

  • 4
  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now