So, if I open a SQL Script in Microsoft SQL Server Management Studio
and save it with a new file name, then edit it, it keeps the old name
in the tab caption. If I keep saving it, it keeps that old name
displayed. I need to close it and reopen it to get the new name
displayed.

Is anyone else seeing this? Is there a fix?

Hello Ion,

This seems some kinda bug. I can verify your observation.

Here's the repro:
- Open an already existed T-SQL Script file
- Using File menu, save this file as another name (Then you'll see that file
is saved as it's new name and the new created file is open now and you are
working on it however it shows the old file' s name)
- You can't open your new created copy file while "the original(!)" is open
because it's the new one and it's already open!

I've tested this behaviour in SQL Server 2008 (10.0.1300.13) and it's still
buggy. I don't think MS developers are aware of this problem. Do you want to
feedback this problem via Connect? If not, I'll feedback. Let me know.

--
Ekrem Önsoy



"Ion Freeman" <ionFreeman (AT) gmail (DOT) com> wrote

Hello Ion,

This seems some kinda bug. I can verify your observation.

Here's the repro:
- Open an already existed T-SQL Script file
- Using File menu, save this file as another name (Then you'll see that file
is saved as it's new name and the new created file is open now and you are
working on it however it shows the old file' s name)
- You can't open your new created copy file while "the original(!)" is open
because it's the new one and it's already open!

I've tested this behaviour in SQL Server 2008 (10.0.1300.13) and it's still
buggy. I don't think MS developers are aware of this problem. Do you want to
feedback this problem via Connect? If not, I'll feedback. Let me know.

--
Ekrem Önsoy



"Ion Freeman" <ionFreeman (AT) gmail (DOT) com> wrote

Hello Ion,

This seems some kinda bug. I can verify your observation.

Here's the repro:
- Open an already existed T-SQL Script file
- Using File menu, save this file as another name (Then you'll see that file
is saved as it's new name and the new created file is open now and you are
working on it however it shows the old file' s name)
- You can't open your new created copy file while "the original(!)" is open
because it's the new one and it's already open!

I've tested this behaviour in SQL Server 2008 (10.0.1300.13) and it's still
buggy. I don't think MS developers are aware of this problem. Do you want to
feedback this problem via Connect? If not, I'll feedback. Let me know.

--
Ekrem Önsoy



"Ion Freeman" <ionFreeman (AT) gmail (DOT) com> wrote

Hello Ion,

This seems some kinda bug. I can verify your observation.

Here's the repro:
- Open an already existed T-SQL Script file
- Using File menu, save this file as another name (Then you'll see that file
is saved as it's new name and the new created file is open now and you are
working on it however it shows the old file' s name)
- You can't open your new created copy file while "the original(!)" is open
because it's the new one and it's already open!

I've tested this behaviour in SQL Server 2008 (10.0.1300.13) and it's still
buggy. I don't think MS developers are aware of this problem. Do you want to
feedback this problem via Connect? If not, I'll feedback. Let me know.

--
Ekrem Önsoy



"Ion Freeman" <ionFreeman (AT) gmail (DOT) com> wrote

Hello Ion,

This seems some kinda bug. I can verify your observation.

Here's the repro:
- Open an already existed T-SQL Script file
- Using File menu, save this file as another name (Then you'll see that file
is saved as it's new name and the new created file is open now and you are
working on it however it shows the old file' s name)
- You can't open your new created copy file while "the original(!)" is open
because it's the new one and it's already open!

I've tested this behaviour in SQL Server 2008 (10.0.1300.13) and it's still
buggy. I don't think MS developers are aware of this problem. Do you want to
feedback this problem via Connect? If not, I'll feedback. Let me know.

--
Ekrem Önsoy



"Ion Freeman" <ionFreeman (AT) gmail (DOT) com> wrote

Hello Ion,

This seems some kinda bug. I can verify your observation.

Here's the repro:
- Open an already existed T-SQL Script file
- Using File menu, save this file as another name (Then you'll see that file
is saved as it's new name and the new created file is open now and you are
working on it however it shows the old file' s name)
- You can't open your new created copy file while "the original(!)" is open
because it's the new one and it's already open!

I've tested this behaviour in SQL Server 2008 (10.0.1300.13) and it's still
buggy. I don't think MS developers are aware of this problem. Do you want to
feedback this problem via Connect? If not, I'll feedback. Let me know.

--
Ekrem Önsoy



"Ion Freeman" <ionFreeman (AT) gmail (DOT) com> wrote

Hello Ion,

This seems some kinda bug. I can verify your observation.

Here's the repro:
- Open an already existed T-SQL Script file
- Using File menu, save this file as another name (Then you'll see that file
is saved as it's new name and the new created file is open now and you are
working on it however it shows the old file' s name)
- You can't open your new created copy file while "the original(!)" is open
because it's the new one and it's already open!

I've tested this behaviour in SQL Server 2008 (10.0.1300.13) and it's still
buggy. I don't think MS developers are aware of this problem. Do you want to
feedback this problem via Connect? If not, I'll feedback. Let me know.

--
Ekrem Önsoy



"Ion Freeman" <ionFreeman (AT) gmail (DOT) com> wrote

Hello Ion,

This seems some kinda bug. I can verify your observation.

Here's the repro:
- Open an already existed T-SQL Script file
- Using File menu, save this file as another name (Then you'll see that file
is saved as it's new name and the new created file is open now and you are
working on it however it shows the old file' s name)
- You can't open your new created copy file while "the original(!)" is open
because it's the new one and it's already open!

I've tested this behaviour in SQL Server 2008 (10.0.1300.13) and it's still
buggy. I don't think MS developers are aware of this problem. Do you want to
feedback this problem via Connect? If not, I'll feedback. Let me know.

--
Ekrem Önsoy



"Ion Freeman" <ionFreeman (AT) gmail (DOT) com> wrote

Hello Ion,

This seems some kinda bug. I can verify your observation.

Here's the repro:
- Open an already existed T-SQL Script file
- Using File menu, save this file as another name (Then you'll see that file
is saved as it's new name and the new created file is open now and you are
working on it however it shows the old file' s name)
- You can't open your new created copy file while "the original(!)" is open
because it's the new one and it's already open!

I've tested this behaviour in SQL Server 2008 (10.0.1300.13) and it's still
buggy. I don't think MS developers are aware of this problem. Do you want to
feedback this problem via Connect? If not, I'll feedback. Let me know.

--
Ekrem Önsoy



"Ion Freeman" <ionFreeman (AT) gmail (DOT) com> wrote