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 |
|
Dennis
Starting Member
11 Posts |
 Posted - 2007-01-25 : 07:27:12
|
| Hi all,I was thinking about schemabinding all of our sps, funcs, and views so that if a table is inadvertantly changed that might "break" one of them an error will occur. Are there any drawbacks to schemabinding? Are there any hidden costs? Thanks in advance |
|
|
Kristen
Test
22859 Posts |
Posted - 2007-01-25 : 07:35:17
|
| My $0.02:We have some options (in our source code) that we use differently between DEV and PRODUCTION. (Like WITH ENCRYPTION which we use only on LIVE). We handle these with comments:CREATE PROCEDURE MySproc/**LIVEWITH ENCRYPTIONLIVE**/ASand we globally change/**LIVE -> /** **/LIVE**/ -> /** **/as part of "deploying" the code.Strikes me that if there is a cost to schemabinding it might be appropriate to only use it for DEV environment (yeah, it would save you from yourself on Production if you failed to run the Scripts int he right order, but your test-rollout to QA/Staging etc. should catch that type of issue.Kristen |
 |
|
|
|
|
|
Schemabinding question