[quote="faiyazu99, post:4, topic:10253, full:true"]
The reason why I am creating views is that one of our integration partner need to access these views. They can only access views through ObjectID. [/quote]
I can't imagine how they are accessing views through ObejctID ... they could just as easily hold the View Name (provided that doesn't change) and use that ... and find the ObjectID from that ... or use an Extended Property, instead of ObjectID to find it via that, it's as broad as it is long - and ALL much easier to manage than the requirement that a VIEW's ObjectID must NEVER change ... but there we go, mine not to reason why, its just that I think that its a daft requirement, because there may well be circumstances where you HAVE to drop the view and then you will NOT be able to reassign it to the original ObjectID period.
Here's an example: Your view is based on an Object with SCHEMA BINDING. At some future point that Schema Bound object needs to change, so your VIEW(s), and anything else depending on it, will have to be dropped first, and then recreated (with new ObjectIDs)
As I said earlier, using ALTER rather than DROP / CREATE will achieve that.