Return to Question

Is there any way to create versioning for stored procedures? I have created an api which fetches data from a database using store procedures. This api is being consumed from a mobile app. I released the v1.0 of api (www.example.com/api/v1.0/endpoints). Now I've to release the v2.0 of the api (www.example.com/api/v2.0/endpoints), and there are many changes both in the api and stored procedures. So how do I release the v2.0 without affecting the older api ? Because even if api is independent, stored procedures are the same for both. How is such kinds of situations supposed to be handled  ?

Is there any way to create versioning for stored procedures? I have created an API which fetches data from a database using stored procedures. This API is being consumed from a mobile app. I released the v1.0 of API (www.example.com/api/v1.0/endpoints). Now I've to release the v2.0 of the API (www.example.com/api/v2.0/endpoints), and there are many changes both in the API and stored procedures. So how do I release the v2.0 without affecting the older API? Because even if API is independent, stored procedures are the same for both. How is this kind of situation supposed to be handled?

I mean I want both sprocs on the db at the same time and to be able to call both, but the problem is they can't have the same name.