Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
lappy
Starting Member
6 Posts |
 Posted - 2009-01-15 : 10:00:05
|
I'm quite new to SQL, and even newer to SQL Server. I've been using SQL Server as part of my job (well, interacting with it) since ~September, and I only graduated in May. However, I've been asked to do some R&D about schemas. We're thinking about changing our schemas so that they make more sense from a business perspective. Currently all our tables dbo. and then the table name has a three letter prefix that determines whether they're static tables, user data, or system data.We're about to add a new section to our website, and since the website first went live there have been several new sections added. These weren't organised out as the team went along so we're in a situation where we have quite a mesh of tables in our 'user data' area. Time to sort ourselves out and apply some good architecture.Are there any gotchas that I should be looking out for when doing this? Obviously we've got live data in the current structure so we can't really change the shape of any of the tables. Is changing schemas relatively painless or are we looking at building a new database and migrating data over? Are there any resources that I should read through to help get me up to speed so that I have a better chance at making this work?!Sorry it's such a general post, but I really don't know where I should be starting to ask more specific questions... |
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2009-01-15 : 22:34:18
|
| If it already went live,I wouldn't touch it. But you can change Schema to other one with:ALter schema....Transfer..<newschema>....(See Booksonline for it) |
 |
|
|
blindman
Master Smack Fu Yak Hacker
2365 Posts |
Posted - 2009-01-16 : 10:01:18
|
quote:
Originally posted by lappy
Currently all our tables dbo. and then the table name has a three letter prefix that determines whether they're static tables, user data, or system data.
Seriously. How much benefit do you get from this?________________________________________________If it is not practically useful, then it is practically useless.________________________________________________ |
|
|
|
lappy
Starting Member
6 Posts |
Posted - 2009-03-03 : 11:33:55
|
| Not much. Its mainly human readable. The three letter prefixs let us know whether or not we should be altering that table from our code. This is why we're thinking of changing it. I guess 'they' just didn't know any better when 'they' created it. |
|
|
|
|
|
|
|
|
SQL Server 2005 Schemas