September 27, 2015 at 11:29 pm
This was removed by the editor as SPAM
September 28, 2015 at 2:14 am
Can you add an alien name as 'NASales' to the existing
instance 'USSales' to achieve the same thing??
ie users will see instance as 'Sales0\USSales', but it points to the original one.....
MCSE Data Platform; BI
MCITP Database Developer; BI
September 28, 2015 at 2:17 am
helenlu7 65408 (9/28/2015)
Can you add an alien name as 'NASales' to the existinginstance 'USSales' to achieve the same thing??
ie users will see instance as 'Sales0\USSales', but it points to the original one.....
You can do that, but that needs to be done on all the clients connecting to that instance, so you can't do that on the server itself.
September 28, 2015 at 3:20 am
In a DB connection string, you can use an ALIEN name for an instance. DNS can resolve it in the domain.... ie the actual server name can be different, sa long as it's alien name remain the same, users connection string still works without change....
MCSE Data Platform; BI
MCITP Database Developer; BI
September 28, 2015 at 5:35 am
Nice question about something I hope I never have to do.
September 28, 2015 at 6:29 am
We just ran up against this. IT set up a new developer's box, and used the default for the SQL named instance. Which was wrong and would not jive with some of the code he needed to run/test. After a bunch of research, we learned about this lovely little limitation.
September 28, 2015 at 6:37 am
Of course, this won't carry over server settings, logins, databases, et al.
So unless this is a new instance with nothing much set up on it, there's a lot more work to do.
September 28, 2015 at 7:27 am
You didn't really say "named instance" in the question. You said "known as". Why would you place a named instance on a single instance server?
September 28, 2015 at 9:23 am
Steve,
This rename can be done using sp_dropserver and sp_addserver @local='local.
I tested this on one of my development boxes that had only a single, default-named instance. First, I ran this:
sp_dropserver '<server>'
go
sp_addserver '<server>\SQLTime', 'local'
go
sp_helpserver
go
The name and network name both came back as '<server>\SQLTime'. After a restart of SQL, I connected with the (single) SQL Server instance '<server>\SQLTime'.
To verify this wasn't an indosyncrasy of the default instance, I repeated the procedure to change '<server>\SQLTime' to '<server>\SQLTim'.
Again, it worked.
This was tested on Microsoft SQL Server 2008 (SP2) - 10.0.4000.0 (Intel X86)
I'm pretty sure the correct answer is sp_dropserver followed by sp_addserver (. 'local').
Thanks,
Tim Bailey
September 28, 2015 at 10:18 am
Bobby Russell (9/28/2015)
You didn't really say "named instance" in the question. You said "known as". Why would you place a named instance on a single instance server?
I can think of a few reasons.
For example, with the SQL Browser service stopped on the server, a named instance isn't advertised over the network. This can reduce the visibility of a sensitive instance, making it harder for attackers to find.
Also, you may be an application developer whose application requires a dedicated instance of SQL Server (Express/MSDE) but you don't want to preclude your clients from using the same machine for other instances.
September 28, 2015 at 3:03 pm
tbailey 19088 (9/28/2015)
Steve,This rename can be done using sp_dropserver and sp_addserver @local='local.
I tested this on one of my development boxes that had only a single, default-named instance. First, I ran this:
sp_dropserver '<server>'
go
sp_addserver '<server>\SQLTime', 'local'
go
sp_helpserver
go
The name and network name both came back as '<server>\SQLTime'. After a restart of SQL, I connected with the (single) SQL Server instance '<server>\SQLTime'.
To verify this wasn't an indosyncrasy of the default instance, I repeated the procedure to change '<server>\SQLTime' to '<server>\SQLTim'.
Again, it worked.
This was tested on Microsoft SQL Server 2008 (SP2) - 10.0.4000.0 (Intel X86)
I'm pretty sure the correct answer is sp_dropserver followed by sp_addserver (. 'local').
Thanks,
Tim Bailey
I've seen this reported, but in all my testing, and the documentation, this doesn't work.
Can you connect remotely? Are you use you're resolving a name from SQL?
September 28, 2015 at 6:20 pm
tbailey 19088 (9/28/2015)
Steve,This rename can be done using sp_dropserver and sp_addserver @local='local.
I tested this on one of my development boxes that had only a single, default-named instance. First, I ran this:
sp_dropserver '<server>'
go
sp_addserver '<server>\SQLTime', 'local'
go
sp_helpserver
go
The name and network name both came back as '<server>\SQLTime'. After a restart of SQL, I connected with the (single) SQL Server instance '<server>\SQLTime'.
To verify this wasn't an indosyncrasy of the default instance, I repeated the procedure to change '<server>\SQLTime' to '<server>\SQLTim'.
Again, it worked.
This was tested on Microsoft SQL Server 2008 (SP2) - 10.0.4000.0 (Intel X86)
I'm pretty sure the correct answer is sp_dropserver followed by sp_addserver (. 'local').
Thanks,
Tim Bailey
I would suggest to have a look at this link
for the moment , this possibility is not allowed to the SQL Server 2016.
Maybe for the 2018 ?
Uninstall and install a stand-alone SQL Server instance is long way but up to now the alone method.
September 28, 2015 at 10:55 pm
September 29, 2015 at 9:41 am
Perhaps some of this works in 2008? Anyone verify this? I've tested in 2012/2014 and it does not work.
Viewing 15 posts - 1 through 15 (of 21 total)
You must be logged in to reply to this topic. Login to reply