January 14, 2013 at 7:11 am
They say it's best practice to name a SQL instance even it's the only instance on the host server. My question is, are there any security risks if I give the SQL instance the same name as the server? Or should I just leave it as the default instance?
---------------------------------------------------------
It takes a minimal capacity for rational thought to see that the corporate 'free press' is a structurally irrational and biased, and extremely violent, system of elite propaganda.
David Edwards - Media lens[/url]
Society has varying and conflicting interests; what is called objectivity is the disguise of one of these interests - that of neutrality. But neutrality is a fiction in an unneutral world. There are victims, there are executioners, and there are bystanders... and the 'objectivity' of the bystander calls for inaction while other heads fall.
Howard Zinn
January 14, 2013 at 12:36 pm
Abu Dina (1/14/2013)
They say it's best practice to name a SQL instance even it's the only instance on the host server.
I have not heard that one. Can you share a reference to the claim that it is a best practice?
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
January 14, 2013 at 1:03 pm
I guess I am confused by that...
All instances installed have to have a name - whether it is the default instance or a named instance. The default instance has a name - which is MSSQLSERVER. All named instances are just that - named....
Referencing a default instance can be done using either the server name or the IP address, whereas referencing a named instance must be done using the server name\instance name or IP:port.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply