January 25, 2018 at 8:04 am
I simply offered an alternative: rather than searching for errors yourself, let SQL find them for using sp_refreshview. Probably on your qa/test system, as the views are likely identical or nearly so. Instead of even considering any possibilities offered by that, you preferred to slam me as completely ignorant of SQL. Wonderful response.
SQL DBA,SQL Server MVP(07, 08, 09) A socialist is someone who will give you the shirt off *someone else's* back.
January 25, 2018 at 8:52 am
You seem fixed to the idea that "every view must be schema bound." That's just not true, and probably not even optimal.
SQL DBA,SQL Server MVP(07, 08, 09) A socialist is someone who will give you the shirt off *someone else's* back.
January 25, 2018 at 9:15 am
You seem fixed to the idea that "every view must be schema bound." That's just not true, and probably not even optimal.
This all started because the original poster asked if anyone had any ideas for maintaining schema bound views with other schema bound views. And while I would suggest that building views upon other views, whether schema bound or not, is probably not a good idea, there are advantages that come with using schema bound views. I'm not sure it's a question of optimal as it is preference This method prevents changes that will affect views that have been built on them. I haven't had a chance yet to review the thread to see where it might have gone of course so jumping in now has some risk. It seems to me that simply saying it's not optimal is perhaps not the most helpful response. What he wants to know is if someone has a good idea for managing views with this configuration. Let him help who can.
January 25, 2018 at 10:09 am
RonKyle - Thursday, January 25, 2018 9:15 AMYou seem fixed to the idea that "every view must be schema bound." That's just not true, and probably not even optimal.
This all started because the original poster asked if anyone had any ideas for maintaining schema bound views with other schema bound views. And while I would suggest that building views upon other views, whether schema bound or not, is probably not a good idea, there are advantages that come with using schema bound views. I'm not sure it's a question of optimal as it is preference This method prevents changes that will affect views that have been built on them. I haven't had a chance yet to review the thread to see where it might have gone of course so jumping in now has some risk. It seems to me that simply saying it's not optimal is perhaps not the most helpful response. What he wants to know is if someone has a good idea for managing views with this configuration. Let him help who can.
Again, just a possible alternative method for finding the problem views. Schema binding could certainly be reimplemented after using sp_refreshview to find the problem areas if you wanted to.
SQL DBA,SQL Server MVP(07, 08, 09) A socialist is someone who will give you the shirt off *someone else's* back.
Viewing 4 posts - 31 through 33 (of 33 total)
You must be logged in to reply to this topic. Login to reply