I installed Named instance in SQL 2005 Server (TESTAVTESTNETAV), now i am not able to acces this instance in SQL Query Ana.throug IP Address.
i am able to access this instance through name
How can i resolve this issue please help me out ??
Hi,
I have sql2005 sp1 active-active installation.
I've fixed the named instance port.
I can't reach it from clients with i'ts name (servernameinstancename) .
I manage to rech it only by using servername, ip-port.
The sql browser has the following error:
"The configuration of the AdminConnectionTCP protocol in the SQL instance GILBOACL is not valid."
your help is appreciated!
Shahar
I have installed and configured a 2nd instance of SSRS 2005 Standard Edition SP1 on a Windows Server 2003 Standard Edition SP2. The 2nd instance is using it's own database and virtual directories under the default website. All configuration steps ran without error. I have no problem accessing the 2nd instance virtual directories via IE. When I connect to Reporting Services via Management Studio, it gives me no options for which instance to access and connects to the default instance. How do I connect to a 2nd named instance of SSRS via Management Studio? I've found no documentation in BOL related to this.
View 3 Replies View Related
This is a slight re-stating from an older thread, which I think warrants some new discussion. The answer has always been that system administrators should have full access to everything on a system, including databases.
Although that is a logical position for internal IT departments it doesn't quite fit the model of systems with outsourced or external system support.
"If you don't trust your DBA, then you need a new DBA. They are in a position of authority for a reason and restricting that authority makes it impossible for them to do the job they are hired to do."
What about scenarios where you have local machine administrators that should NOT be given access to private data in a secured database, even though they need to be able to access and maintain everything else? And unfortunately some regulations are written about access to stored data whether encrypted or not...
In the modern world of Sarbanes-Oxley and PCI-DSS/CISP it is no longer so cut and dried. Especially where companies have software/hardware support contracts with third parties that require administrative access to other aspects of the systems.
So accepting that you might need someone to have administrative level access to the box but they should not be able to view the contents of a database installed on that box, what would you do?
Is there a way to create an adminstrative group that does not allow access to a specific named instance of SQL?
Is there a way to revoke access for one member of the administrators group only?
Thanks,
Ted
Good Day,
I am creating a SQL Named instance as a testing environment. This instance is on the same physical box as my Development environment, both are SQL 2005 standard edition. From the server in Management Studio, I can load, and interact with both instances. From a remote connection (e.g., my pc) I cannot access the named instance. I am getting the following:
Connect to Server
X Cannot connect to <server><named instance>
Additional Information
An error has occured while establishing a connection to the server. When connecting to SQL Sever 2006, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)(Microsoft SQL Server)
I have checked, and rechecked the server settings for this named instance, and remote connections are set to "allow" I have enabled TCPIP and Named Pipes prototocals, and have ensured that my firewall is allowing the "listenting port" for the named instance, and have even tried turning off my XP firewall during testing.
I am sure that I have probably missed something, and have searched the community but only have been able to find resolutions that I have already tried. Is there more?
Thanks in advance for any help and guidance you can provide.
I try to connect from a pc to a SQL Server on another pc. Both pc’s are in a workgroup. I want to connect from a Windows Forms application to a named instance on the other computer. By now I have been able to connect from one pc to SQL Server on the other with tcp:smurfin, 52782.
I want to be able to use servernameinstancename (instead of portnumber) to make a connection in a Windows Forms application.
I’ve checked / tried te following:
•In the properties of the instance, tab Connections, the option Allow Remote Connections is enabled
•In Configuration Manager: TCP is enabled
•The service SQL Server Browser is started
•On the tab IPAddresses, in the section IPAll, there is NO portnumber for TCP Port. And TCP Dynamic Ports has the nummer 52782
•I have created un inbound rule for port 52782 and also for 1434 (SQL Server Browser). And to be on the save side: a rule for 1433 as well.
•Restarted the service
If I run the following code in SQL Server, that same port number (52782) is returned:
EXEC xp_ReadErrorLog 0, 1, N'Server is listening on', N'any', NULL, NULL, 'DESC'
GO
SELECT local_tcp_port
FROM sys.dm_exec_connections
WHERE session_id = @@SPID
[Code] ....
I've two instances(Default, Named[dynamicsFINANCE]) running on SQL server 2014. However, when I try to connect to named instance say (dynamicsFINANCE) using SQL authentication from local SSMS, I get below error message:
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)
I assigned a static port number to the named instance [dynamicsFINANCE] 1450. I also setup the firewall rule to allow access to Port 1450.
I have a 3 node cluster on which I have installed SSAS as it's own insntance. I have created this as a named instance and can connect to it by serverinstance if I'm on the server itself. However from my desktop I get the error saying instance was not found on server name.
I have defined an alternate port and setup firewall rules and can connect via server:port but not serverinstance. Prior to making this change SSAS was running on default port of 2383 and I could connect just by servername.
I have read many articles for previous versions saying that clustered SSAS will always use 2383 and that you must connect just using servername. However and this is were it gets strange. I have a 2 node UAT cluster with SSAS setup exactly the same way I've described above and I can connect from my desktop as serverinstance.
Should I be able to connect as serverinstances for a named clustered instance in 2012 ?
Hi, I have a task in hand to migrate (upgrade) from SQL2K named instance to SQL2K5 default instance. There are many intranet applications touching current SQL2K. I would like to perform this upgrade such that I don't have to touch any application code - meaning I don't have to change the connectionstring to point to new Default instance. How can I achieve this?
So, in otherwords, here is what I want to achieve:
Current Server: SQL2K: SERVER_AINSTANCE_A (named instance)
Upgraded Server: SQL2K5: SERVERB (default instance)
If I have both default, I could achive this by setting up DNS alias after migration done so that any call for SERVER_A would point to SERVER_B. But in my case, I don't have SERVER_A, I have named instance. Is there any solution?
Regards,
Vipul
Hi everyone,
Is there a way to route a specific IP address to a named instance on a SQL 2k system???
thanks
tony
I am trying to set up a Named Instance of SQL 2000 on the same machine that has a default instance of SQL 7.0. The setup always completes and I am able to register the Named Instance of the SQL Server with which it was installed on. However, when I try to connect the users to the database, with both windows and SQL authentication, I receive a SQL server not found error. I have tried an alias setup as well as physically specifying the port number in settup up an ODBC connection.
Has anyone ran into similar problems?
Also, has anyone been able to successfully complete the process as mentioned above?
I have a server with sql server 2005 installed as the default instance -- I have a piece of software that needs SQL2000 to be the default instance. Is there a way other than install new sql2005 named instance and move databases to rename my SQL2005 instance from <machinename> to <machinename>sql05 for example?
Bryan
I have SQL Server 2000 Standard Edition (sp3a) running on a windows 2003 (sp4) Server.
It is a Production Server with 3 NAMED Instances and NO Default Instance.
Does anyone know if I can rerun the SQL Server Install and add a DEFAULT Instance to this box without disrupting the other Named Instances???
I installed SQL Server 2005 recently on a cluster. I didn't go for the default instance and instead I named the instance option. Now I would like to migrate everything from the named instance to the default instance, which I haven't yet installed.
Is this an easy process? What about the logins and the maintenance plans and jobs? Is there anything else I need to be aware of?
Hi
I've never had to do this, but when I downloaded the Web Workflow Approvals Starter Kit, it requested that I install the database into a User Instance of .SQLEXPRESS.
Now the problem is, I've installed it onto a default instance, so I was wondering whether you can create a named instance on top of a default instance... and if so, how would you do that?
Cheers
Chris
The box I am trying to connect to is running two instances of SQL Server.
There is a SQL Server 2005 instance which is the default. There is a SQL Server 2000 instance which is named 'SQLSERVER'.
I can connect to the SQL Server 2000 instance no problem:<add key="ConnectionString" value="server=MYPCSQLSERVER;database=mydatabase;user id=****;password=****" />
However, I am having trouble connecting to the Default SQL Server 2005 instance. I have tried:
<add key="ConnectionString" value="server=MYPC;database=mydatabase;user id=****;password=****" />
but it doesn't work. I have tried explicitly setting SQL Server 2005 to use port 1434 (as SQL Server 2000 is running on port 1433), and then used:
<add key="ConnectionString" value="server=MYPC,1434;database=mydatabase;user id=****;password=****" />
but this doesn't work either.
Am I mssing something here? Any help much appreciated
Thanks...
If you were asked to install SQL 2005 on a machine, would u install a default instance or a named one? And why would u choose one over the other?? Also, r there any issues with using a default instance?
Thank you for all your help.
In our lab we have 2 clustered instance of Sql server 2018R2 as follows
Virtual Server Name
IP SqlVir 10.1.1.6
SqlVirDr 10.1.1.12
The Data is SqlVir is replicated manually every day to SqlVirDr.
We had to change the Virtual Server name of SqlVirDr to SqlVir so that all dot net applications accessing SqlVir could continue to access the database without changing the application string.
For that purpose I deleted the computer name SqlVir from the domain and its IP 10.1.1.6 from DNS. Then I went to the failover cluster manager of SqlVIrDr right clicked the Sql services selected the properties and changed the DNS name from SqlVirDr to SqlVir.The applications then could access the data.However when I changed the network IP address from 10.1.1.12 to 10.1.1.6 the Sql services was found to be down.
Perhaps the procedure I followed in deleting the computer name from domain and the IP from DNS was wrong.What exactly is the steps that I should follow to achieve the above objective.
We have an Sql Server 2008R2 Clustered production instance by name 'ProdVir' configured in 2 nodes(Active-passive) withWIndows Server 2008 R2. We also have another clustered instance as disaster recovery by name 'VirDr' configured again in another 2 nodes of Windows Server 2008 R2. Every day morning there is mainatenace plan which backups all the database in production and another maintenace plan in the disaster recovery server 'VirDr' which restores the backups into the VirDr instance.
I would like to know that in an eventuality of a disaster in the clustered production instance of 'ProdVir'. could we rename the the instance VirDr(meant for disaster recovery) to ProdVir and also change the Ip addresses accordingly so that the application programs do not have to change the details for the datasource in the connection strings.
I am running SQL2k SP3 with a default instance. I have recently added a second, named instance. When I try to connect to the named instance through Enterprise manager, it often times out. I never get a timeout accessing the default instance. Is there something I missed when setting up the second instance that is causing this access delay?
Thanks,
Ken Nicholson
What is the easiest way to check wether a server has named instance or not? Is there a command from DOS?
------------------------
I think, therefore I am - Rene Descartes
Hi,
How can i connect to Named Instance of MSDE on remote server from Enterprice Manager in my local computer ?
Instance name is Helm
I can connect inside server like
osql -S -E .Helm
But how i access from remote machine using Enterprice Manager ?
Regards,
Yujin Boby
Hi, all.
To use Named instance on the same machine, Do I need to check any license issue?
My Company has one server license and wants to use Named instance.
thank you..
Hi,
I did install SQL-server developer edition. During the installation it asked me the name of de instance. I let the installation create the default Named instance.
Now I want to add an instance with a new name. What is the best way to do this? Is this the same as creating a Notification service?
Doeb
I have sql2000 and sql2005 on one machine.
When I try to query a named instance of sql2005 from query analyzer in sql 2000 I recieved an error regarding an entry not being in the sysservers table. I added an entry pointing to the new install of sql2005. Now I get an error message saying
Server: Msg 170, Level 15, State 1, Line 2
Line 2: Incorrect syntax near '-'.
My server name is BB-SERVER1 It definitly does not like the hyphen. Any thoughts?
Changing the server name is not really an option.
Greg
We want to rename our instance and I understand there isn't a straightforward way to do so. I'm prepared to run SQLEXPR again to create the new named instance. However, I'm not clear on how to remove the other named instance once the data files have been moved over. I do not want the old service "SQL Server (<old_named_instance>)" to be running. I would also like the files "C:Program FilesMicrosoft SQL ServerMSSQL.1" removed along with the registry entries for this instance.
I tried running SQLEXPR with a /? option but that invoked the installer and did not give me the command line options. Is there a simple way to remove a specific named instance? Thanks.
Hi everybody,
Here is my problem: I'm setting up a new computer with SQL 2005 to replace the old one with SQL 2000. What I want to do is to transfer all the data from the SQL Server 2000 to the 2005 then rename the 2005 from the temp name to the same name as the SQL 2000, so all the pages can connect to the 2005 instead of the 2000. The problem right now is that all of the pages that that are being published within the network is calling the SQL 2000 by it instance only eg: Data Source = MainSQLServer. With the SQL 2005 I can't just call the instance in the connection string, it requires that the computer's name and the instance be provided, eg: \computer_nameinstance_name. I can't go back and edit every single one of the pages being served. So I need to configure the SQL 2005 in a way that all of the existing pages can access it with the same connection string that is in use right now to connect to the SQL 2000.
Thanks for the help!
As understand it, the only way to add another SQL Express 2005 named instance is to run SQLEXPR32.EXE again. However, when you to, right at the end, you get the following error message:
"An installation package for the product MS SQLK Server VSS Writer cannot be found. Try the installation again using a valid copy of the installation package 'SQLWriter.msi'"
So, I deleted all named instances, and the repeated the procedure and did not get this error and it installed fine. Obviously, I would not be able to delete all instances, but in this case it didn't matter.
So, here are my questions:
Question 1) Am I correct you must rerun SQLEXPR32.EXE to create a new named instance? (I think the answer is yes)
Question 2) Is there a way to rename an existing named instance? (I think the answer is no)
Question 3) The install/uninstall for SQLEXPR32.EXE is incredibly buggy. I have spend days trying to remove an named instance with no succes. Once your remove all named instances from Control Pannel, you stll have not removed SQL Express 2005. How do you remove it? We are considering other avenues because of the incredible problems with this product. Also, we inadvertantly installed SQL Express 2005 Advanced Services, when we meant to install SQL Express 2005, so we would like to uninstall Advance Serviuces and reinstall SQL Express 2005
Question 4) I am switching from the Outlook Express newsgroups to these groups. In the context of these groups, what is the difference betwee a Forum and a Newsgroup?
Thanks
Bob
Hi There
I cannot find anything online or in BOL about the proper format for a named instance in the routing address.
is it simply
ADDRESS = 'TCP://SERVERNAMEINSTANCENAME:4026'
or do you need to provide the port number for the instance.Not sure if TCP recognises the instance part?
Thanx
Hi all,
I have some questions regarding Clustering.
(1) Can we create Default Instance & Named Instance in the clustering environment (i.e.) two instances in clustering on same hardware.
The idea here is , to put some highly transactional databases on default instance ( and giving 5 CPU's to Default instance ) and on the Named Instance ( giving 3 CPU's for Named Instance) in CLUSTERING ENVIRONMENT.
(2) Can anyone guide me , how can we restrict the instances to take 5 Cpu's & 3 Cpu's repectively Iin CLUSTERING ENVIRONMENT.
Thanks.
Thanks for Microsoft's Windows XP Service Pack 2 and Windows Server 2003 that make the security much stronger. However, besides the invisible benefit so far, I have become the victim of this security policy.
I have several named instances of SQL 7/2000 installed in my machine. They are not visible out of the Microsoft new fire wall. I need to access the instances from outside the fire wall, but I don't know which port I should open for the instances.
From SQL online, the default instance of SQL server is connected through TCP/IP by default port 1433. I could successful open that port and made the default instance visible to outside. However, the port 1433 doesn't work for the named instances. SQL online said, the port for named instance is dynamically (by default) chosen the first time the instance is started. So, actually, I have no way to know the port.
Is there anyway that I can check the database or somewhere to get the port that is used by the named instance?
Thanks for any input and recommendation.
We have a two node activepassive SQL Server 2000 cluster SP2 running on Window 2000 advanced server SP2. Everything is working fine including failover. Today we migrated over our 7.0 databases to the SQL cluster and they attached fine and upgraded fine but we would like to shutdown the 7.0 server and bring up the clustered SQL Server under the old name. We will be running 3 instances of SQL Server 2000 on the Cluster so at least 2 of these will be named instances like this: "Virtual serverinstance". Is it possible to create an alias for this SQL Server so that we could access the server under the original name of the server???
Thanks!!!
Bruce
Hi All,
We have two Baan erp servers 1) SQL2005 on windows 2003 server 2) SQL2000 on windows 200 server.
SQL 2005 server has two database instances, one being the default and the other one as a named instance.
We have been trying to access the data in these two database instances from the second server for our baan erp application on it. Now, we are able to see the data for default instance, but if we try to fetch the data from named instance we end up getting dberror 17.
We tried to register the named instance on the second server using "new sql server registration wizard" in sql 2000 enterprise manager, but there also the list only shows the default instance from sql 2005 server. I tried to type in the named instance and register (both windows and sql server authentication), but end up getting error "Database instance doesn't exist or access denied".
So, for some reason, the named instance from sql 2005 server is not getting published on the network. Please suggest some ways to get around this issue.
thanks,
Jatin