Opening a stored procedure file multiple times in sql server management studio In Sql Server Management Studio, there is strange situation that made me lose a full day work. It is the problem of opening database objects multiple times. When I try to edit a table by right clicking from the object explorer, it is opening the edit screen for the first time, at second time it is re-opening the previously opened but not in a new edit screen. Despite that, if I try to select from that table by right clicking from the object explorer, it is opening the new query with the select statement multiple times while I retry this process. It is also doing exactly the same thing for the stored procedures and functions. I lost my changes in a stored procedure because of opening multiple times.In Visual Studio it is not possible to re-open a file in new editor multiple times by default. Are there any option to reconfigure sql server management studio to not open an object which is already opened in editor?

Note: I know this is my problem to remember which objects I have already opened, but I am asking for help, if there is an option that I am not aware.

Important EDIT:
I need to clarify that I can understand the SQL programming and I am not a newbie. I just don't used to SSMS and I don't know the all features of that tool. In my question's Note Section, I marked that it is my responsibility to keep records of scripts. I am only asking for if there is an option to prevent opening same script multiple times. If your answer is not more than suggesting to using third-party tool etc. please keep it for yourself.
No, there is no such option.

SSMS doesn't open the database object and lock it down for you like Visual Studio w/ Data Tools add on does. Instead, it generates a sql script depending on what you want to do. It is more of a "Oh, you want to modify 'dbo.sp_awesomeness'? Not a problem! Here is the sql script containing alter procedure code you need at the time you asked of it." 2 minutes later, you ask again, and it pops open a new window going thru the same as above. It is always giving you the information at the time of the request to SSMS.

Visual Studio does the "Oh hey, you want the dbo.sp_awesomeness! Sweet. I see you checked it out of git hub, that's all good. Here is the copy." When you ask for it two minutes later, it just brings up the original screen. But then again, you are not creating sql scripts from SSDT. You are building a database package to deploy.