|
|
|
SSCertifiable
       
Group: Moderators
Last Login: Thursday, May 09, 2013 12:38 PM
Points: 6,462,
Visits: 1,384
|
|
|
|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Monday, June 27, 2011 2:01 PM
Points: 7,
Visits: 15
|
|
Hi Andy,
I'm curious to whether you'd recommend this approach for a particularly gnarly database I've inherited. It uses a concept of "partial text" for it's keys. For example, 2007-000123-001 might be the key in a table. The first 11 characters is, in essence, the primary key of the parent table in a parent-child hierarchy. The -001 makes it unique in the child table and also gives it a sequential order.
As you can imagine, it's painful because searches invariably rely upon substrings or LIKE clauses. I know that's killing the performance.
My thought was that I could use this computed column approach to slowly migrate us out of this hell, while still maintaining legacy support. I'd be curious to hear your thoughts.
Great work!
-Mike L
|
|
|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Wednesday, August 01, 2012 2:41 PM
Points: 2,
Visits: 21
|
|
| I was wondering what the performance advantages are between a derived field in a view and computed field in a table. Would you do one over the other because one performs better?
|
|
|
|