March 7, 2006 at 9:55 am
Hi all,
We have just moved everything onto a new Development database server here and was passed the server name on which this database server exists. Now, if I right-clicked on a Server instance in Enterprise Manager and selected 'New SQL Server Registration' and entered the server name this way, Enterprise Manager won't find the database server. But, when I openned up the SQL Server Client Network Utility and added an Alias and doing the relevant things (such as selecting TCP/IP, specifying a port number and IP address), and then going back into Enterprise manager to add a new SQL Server Registration the alias is in the list and I can connect fine.
So what are the main reasons for using the SQL Server Client Network Utility, and what are the benefits against just registering SQL Server databases in Enterprise Manager?
Hope this makes sense, if not let me know and I will adjust the question.
Thanks
Tryst
March 7, 2006 at 10:40 am
Client Network Utility is a tool to specify connection properties for an alias (specific name). This connection properties includes the protocol for the first place, server name / IP, port if applicable etc. This alias entry will be used by ALL front ends including Enterprise Manager, Query Analyzer, you custom applications, data sources etc.
Moreover, this entry can be modified by the attempt to create a Data Source when you click Client Configuration button, change the connection paramaters, return back to ODBC Administrator but don't save the Data source at all. Alias properties will be already modified by this action.
There are several reasons that you Enterprise manager could not find the database server including a different domain. Try to use Fully Qualified Domain name or IP address when registering the server in Enterprise Manager
But as you correctly noticed, it is convenient to create an alias in the Client Network Utility that will specify all connection properties and give this alias an easy name.
Regards,Yelena Varsha
March 8, 2006 at 2:43 am
ok - thanks for the insight on it.
Tryst
March 8, 2006 at 10:15 am
It does sound like a type of network issue. You should ping the server short name and the server long namr (FQDN). Based on the results your network folks can make the appropriate adjustments to DNS and/or WINs.
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply