Random named instances

If for example I was to create a program that added buttons at certain time intervals (and this process could occur forever - i.e. keep adding a button every 30 seconds until the window is closed), and these buttons had ActionListeners attached, meaning they needed to have different names - how would I make it so it would create button1, button2.....buttonx
What I mean is how would I do JButton buttoni = new Jbutton(i)
With i being an incrementing integer.

they don't need different names. the variable you declare as a JButton isn't the JButton, it's just a pointer to it. you can happily just call new JButton forever without assigning the result to anything, or you can assign the result to the same variable over and over. the other JButtons will still exist, and you can get hold of them when you need to via the actionListener. they can all use the same actionListener, too, if you want
for(int i = 0; i < 10; i++) {
   JButton button = new JButton();
   button.addActionListener(this); // or however you want to add it
   // add to your container here, however you like
}one variable. ten buttons. whenever actionPerformed is invoked, you can get hold of the right button from the event

Similar Messages

  • While connecting to the default instance from out side of the server it's reaches to Named instance ?i

    Hi All,
    We have two named instance in "test" server. the names like test\a & test\b... The tcp\ip for test\a is dynamic and for test\b is default port 1433... Now customer requested to install the default instance...we had an issue with installation
    that is the default port number is in use so, the default installation failed and then i changed the settings in registry to use the dynamic port for default instance and then i manually start the sql servers...seems all are good...but when i connecting this
    default instance from out side of the box through SSMS it's pointing to the named instance which one having the default port number(test\b).
    We can change the port number for test\b and assign that port to default instance...but the applications which are connecting to the test\b those are using the default port number...so, we don't want to disturb the connectivity...
    is there any way to fix this issue with out changing the port number for test\b ?
    it is urgent...we have to fix this issue ASAP.. 
    Thanks in Advance,
    rup

    Hi rup,
    Glad to hear the issue is resolved.
    As your post, if SQL Server is configured to use dynamic port,
    it is difficult for application connectivity because the port number selected changes every time that the Database Engine is started.
    From your description, you have changed the dynamic port number to static port number. To avoid a common pitfall, please also ensure that 
    you have deleted the entry (0 or some random port) for dynamic port in SQL Server Configuration Manager. For more details, please review this
    blog.
    Thanks,
    Lydia Zhang
    Lydia Zhang
    TechNet Community Support

  • SQL Server 2012 - 3 SQL clustered instances - one default/ two named instances - how assign/should assign static ports for named instances

    We have two physical servers hosting 3 SQL 2012 clustered instances, one default instance and two named instances.
    The default instance is using port 1433 and the two named instances are using dynamic port assignment.
    There is discussion about assigning static port numbers to the two named clustered SQL instances.
    What is considered best-practice?  For clustered named instances to have dynamic or static ports?
    Are there any pitfalls to assigning a static port to a named instance that is a cluster?
    Any help is greatly appreciated

    Hi RobinMCBC,
    In SQL server the default instance has a listener which listens on the fixed port which is TCP port 1433. And for the named instance the port on which the SQL server listens is random and is dynamically selected when the named instance of the SQL server
    starts.
    For Standalone instance of the SQL server we can change the dynamic port of the named instance to the static port by using SQL server configuration manager as other post, however, in case of the cluster, when we change the port no. of the named instance
    to the static port using the method described above, the port no. again changes back to the dynamic port after you restart the services. I recommend you changing the Dynamic port of the SQL Server to static port 
    on all the nodes , disabling and enabling the checkpointing to the quorum.
    For more information, you can review the following article about how to change the dynamic port of the SQL Server named instance to an static port in a SQL Server 2005 cluster.
    http://blogs.msdn.com/b/sqlserverfaq/archive/2008/06/02/how-to-change-the-dynamic-port-of-the-sql-server-named-instance-to-an-static-port-in-a-sql-server-2005-cluster.aspx
    Regards,
    Sofiya Li
    Sofiya Li
    TechNet Community Support

  • Cannot connect to a named instance using SSMS from a remote machine

    Hi all,
       SQL Server.....: 2012 EE
       OS...................:  Windows Server 2008 R2
       I have a desktop machine, that i am using to administrer SQL Server (via SSMS) and to develop my SSIS solutions, but i can't connect to a named instance of my SQL Server. When i try to connect using SSMS to my named instance (myhost\DWSERVER)
    i get a huge error message:
    A network-related or instance-specific error occurred while establisinh a connection to SQL Server. The server was not found or was not accessible. Verify that the instance is correct and that SQL Server is configured to allow remote connections.
    (provider: TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.) (Microsoft SQL Server, Error: 10060)
    Locally, i am able to access that named instance using SSMS, just when i try to access from another machine, the above error pops-up to me.
    I am using the SQL Server Authentication mode to connect to the named instance.
    What am i doing wrong?
    Thanks in advance.
    Fabrício Pedroso Jorge Database Administrator - Belém, Pará, Brazil

    Hi,
       thanks for your attention.
       That's correct, i can connect to my default instance both locally and remotelly. The default instance in on port 1433. I cannot find the port used by the named instance (DWSERVER).
       Actually, i found this on the errorlog from the named instance:
       2015-03-22 10:10:45.80 spid13s     Server is listening on [ 'any' <ipv6> 49411].
       2015-03-22 10:10:45.80 spid20s     Server is listening on [ 'any' <ipv6> 5023].
       2015-03-22 10:10:45.81 spid20s     Server is listening on [ 'any' <ipv4> 5023].
       2015-03-22 10:10:45.81 spid20s     The Database Mirroring endpoint is now listening for connections.
       2015-03-22 10:10:46.12 spid13s     Server is listening on [ 'any' <ipv4> 49411].
       2015-03-22 10:10:46.25 spid13s     Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\DWSERVER ].
       2015-03-22 10:10:46.26 spid13s     Server local connection provider is ready to accept connection on [ \\.\pipe\MSSQL$DWSERVER\sql\query ].
       2015-03-22 10:10:46.26 Server      Server is listening on [ ::1 <ipv6> 49412].
       2015-03-22 10:10:46.26 Server      Server is listening on [ 127.0.0.1 <ipv4> 49412].
       I can ping normally to the remote server.
    Fabrício Pedroso Jorge Database Administrator - Belém, Pará, Brazil

  • Error"Failed to open the connection"  - Named Instance of SQL Server 2005

    "Failed to open the connection" error, when connecting to the Named Instance of SQL Server 2005
    The report is throwing error, when changing the logon information dynamically through C#.
    Code
         string reportPath = @"D:\NET\TestReport\TestReport.rpt";
         ReportDocument reportDocument = new ReportDocument();
         reportDocument.Load(reportPath);
         foreach(CrystalDecisions.CrystalReports.Engine.Table table in tables)
              TableLogOnInfo tableLogonInfo = table.LogOnInfo;                         
              tableLogonInfo.ConnectionInfo.ServerName = @"TestServer\Instance1";  //Connnecting to Named instance of SQL Server 2005
              tableLogonInfo.ConnectionInfo.UserID = "sa";
              tableLogonInfo.ConnectionInfo.Password = "password";
              tableLogonInfo.ConnectionInfo.DatabaseName = "TEST_DB";
              table.ApplyLogOnInfo(tableLogonInfo);     
         crystalReportViewer1.ReportSource = reportDocument;
    Error Message
         Failed to open the connection.
         Failed to open the connection.
         C:\DOCUME1\PUGALE1\LOCALS~1\Temp\{DF9593A5-5C80-4CBC-ABC3-EC4EF204A7EB}.rpt
    The error is occuring only whenever i am connecting to the Named Instance of SQL Server 2005.
    Thanks in Advance
    Edited by: pugalendran p on Feb 2, 2009 10:32 AM
    Edited by: pugalendran p on Feb 2, 2009 10:43 AM

    Hi,
    Following solution might help you to resolve the issue.
    Solution1:
    Issue happens because universe connection to the Database is not responding and the Data Source Name is not configured to write SQL Server 2005 database.
    Resolution
    Created new DSN connection under SYSTEM DSN to SQL Server 2005 Database.
    Import the universe from the designer.
    Go to File->Parameters.
    Edit Connection.
    On the Database Middleware Page expand SQl Server 2005->Select SQL Server 2005 driver.
    Change the DSN to new DSN connection
    Test the connection.
    Save the Universe and Export it to the repository.
    Solution2:
    I am taking Oracle as an example over here.
    This can be caused when the SQLNET.ora is located in a remote location using mapped drives.
    Resolution
    To resolve,
    check the registry [HKLM\SOFTWARE\ORACLE] you should see a folder called HOME0
    look for any paths that contain a mapped drive partition
    Change the mapped drive letter to a UNC path (
    server\folder)
    Open a command prompt and do a tnsping using the tnsname and verify the location of the SQLNET.ora or TNSNAMES.ora
    If the path is not updated to the new path
    Reboot the server
    Regards,
    Sarbhjeet Kaur

  • Can we install a new mssql cluster on the same windows cluster which already containes a mssql cluster with named instance

    We have a MSSQL 2008R2 Enterprise edition with a two node active passive fail-over cluster running on 2008R2 windows cluster with out any issues,
    Now my question is can we add one more MSSSQL cluster instance for the same setup with out disturbing the existing one ?
    Also give thoughts on load sharing as the second node is mostly ideal now except fail-over scenarios,
    Why we go for this situation is because of the collation setting which can be set only one per instance(Database collation setting change not working), we need a different default collation for the new setup

    hi,
    >>Now my question is can we add one more MSSSQL cluster instance for the same setup with out disturbing the existing one ?
    Yes it is possible .You need to add new drives as cluster aware and install SQL server and put data and log files on thse drives.YOu would need to create named instance of SQL server and need to create different resource group.Both old installation and new
    onw would work separately.
    >>Also give thoughts on load sharing as the second node is mostly ideal now except fail-over scenarios,
    Good point indeed.You are about to create Multi instance cluster and should plan for scenario where one node is down and other node is handling load for both instances.Memory and CPU should be enough to handle the load.
    >>Why we go for this situation is because of the collation setting which can be set only one per instance(Database collation setting change not working), we need a different default collation for the new setup .
    Just for collation if you are installing new instance seems little wierd to me.You can manage collation at column ,database and at server level.
    http://technet.microsoft.com/en-us/library/aa174903(v=sql.80).aspx
    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

  • How to change the name of the named instance in MS sql server 2008 R2

    Hi Gurus
    I have installed a  SAP ECC 6 ehp4 on MS sql server 2008 R2 with MS windows 2008 R2 OS.  While installing sql server i have selected  named instance from  window(default instance, named instance).   and given name  QAS.
    and installed ECC6 ehp4 ABAP engine successfully. now i want to change the name of mssql server's named instance name to DEV.
    kindly let me know
    which one is the best and easy solution
    1. changing the name of named istance at database level and SAP.
    2. or uninstalling  the existing SAP, DB and start from scratch.
    if first is the best, what would be the steps
    Thanks in advance
    balaji

    Hello,
    Please check this note:
    11692 - Renaming the system ID
    regards,
    John Feely

  • Error while installing the named instance SQL 2012 Sp1

    Hi,
    I am getting below error while installing the named instance with features Data base engine. on same server box 2 named instance already installed and working...please suggest. i have done a lot of troubleshooting..(configure local system for Db engines
    during installation, tried to install after another domain ID., repair and uninstalled existing and retried.) .. please s if i need to do anything else to resolve the issue.. installation account is domain admin account...
    Can i rename the installation domain account profile from sql server that used for 2 named instance and for 3 rd named instance i am trying... is any impact after profile rename from the local sql server on any instance already configured...
    Shailendra Dev

    thanks alberto.
    here is 
    2015-03-24 19:48:49.42 Server      Microsoft SQL Server 2012 (SP1) - 11.0.3000.0 (X64) 
    Oct 19 2012 13:38:57 
    Copyright (c) Microsoft Corporation
    Standard Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: ) (Hypervisor)
    2015-03-24 19:48:49.42 Server      (c) Microsoft Corporation.
    2015-03-24 19:48:49.42 Server      All rights reserved.
    2015-03-24 19:48:49.42 Server      Server process ID is 3460.
    2015-03-24 19:48:49.42 Server      System Manufacturer: 'Xen', System Model: 'HVM domU'.
    2015-03-24 19:48:49.42 Server      Authentication mode is WINDOWS-ONLY.
    2015-03-24 19:48:49.42 Server      Logging SQL Server messages in file 'D:\Program Files\Microsoft SQL Server\MSSQL11.SCSMDB\MSSQL\Log\ERRORLOG'.
    2015-03-24 19:48:49.42 Server      The service account is 'AIRWORKS\scadmin'. This is an informational message; no user action is required.
    2015-03-24 19:48:49.42 Server      Registry startup parameters: 
    -d D:\Program Files\Microsoft SQL Server\MSSQL11.SCSMDB\MSSQL\DATA\master.mdf
    -e D:\Program Files\Microsoft SQL Server\MSSQL11.SCSMDB\MSSQL\Log\ERRORLOG
    -l D:\Program Files\Microsoft SQL Server\MSSQL11.SCSMDB\MSSQL\DATA\mastlog.ldf
    2015-03-24 19:48:49.42 Server      Command Line Startup Parameters:
    -s "SCSMDB"
    -m "SqlSetup"
    -T 4022
    -T 4010
    -T 1905
    -T 3701
    -T 8015
    2015-03-24 19:48:49.69 Server      SQL Server detected 1 sockets with 1 cores per socket and 2 logical processors per socket, 2 total logical processors; using 2 logical processors based on SQL Server licensing. This is an informational message;
    no user action is required.
    2015-03-24 19:48:49.69 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
    2015-03-24 19:48:49.69 Server      Detected 15624 MB of RAM. This is an informational message; no user action is required.
    2015-03-24 19:48:49.69 Server      Using conventional memory in the memory manager.
    2015-03-24 19:48:49.98 Server      Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
    2015-03-24 19:48:50.01 Server      This instance of SQL Server last reported using a process ID of 5124 at 3/24/2015 7:48:48 PM (local) 3/24/2015 2:18:48 PM (UTC). This is an informational message only; no user action is required.
    2015-03-24 19:48:50.03 Server      Node configuration: node 0: CPU mask: 0x0000000000000003:0 Active CPU mask: 0x0000000000000003:0. This message provides a description of the NUMA configuration for this computer. This is an informational message
    only. No user action is required.
    2015-03-24 19:48:50.07 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
    2015-03-24 19:48:50.30 Server      Database Mirroring Transport is disabled in the endpoint configuration.
    2015-03-24 19:48:50.58 spid5s      Warning ******************
    2015-03-24 19:48:50.65 spid5s      SQL Server started in single-user mode. This an informational message only. No user action is required.
    2015-03-24 19:48:50.66 spid5s      Starting up database 'master'.
    2015-03-24 19:48:50.90 spid5s      9 transactions rolled forward in database 'master' (1:0). This is an informational message only. No user action is required.
    2015-03-24 19:48:51.04 Server      CLR version v4.0.30319 loaded.
    2015-03-24 19:48:51.17 spid5s      0 transactions rolled back in database 'master' (1:0). This is an informational message only. No user action is required.
    2015-03-24 19:48:51.17 spid5s      Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
    2015-03-24 19:48:51.39 Server      Software Usage Metrics is enabled.
    2015-03-24 19:48:51.81 spid5s      SQL Server Audit is starting the audits. This is an informational message. No user action is required.
    2015-03-24 19:48:51.83 Server      Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
    2015-03-24 19:48:51.86 spid5s      SQL Server Audit has started the audits. This is an informational message. No user action is required.
    2015-03-24 19:48:52.02 spid5s      SQL Trace ID 1 was started by login "sa".
    2015-03-24 19:48:52.16 spid5s      Server name is 'AWISCDB\SCSMDB'. This is an informational message only. No user action is required.
    2015-03-24 19:48:52.35 spid12s     The certificate [Cert Hash(sha1) "151C8B90A9A8AF12F5EFAE3439F691E2C01A7355"] was successfully loaded for encryption.
    2015-03-24 19:48:52.35 spid12s     Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SCSMDB ].
    2015-03-24 19:48:52.40 spid12s     Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag 7806.
    This is an informational message only. No user action is required.
    2015-03-24 19:48:52.43 Server      The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Windows return code: 0x490, state: 16. Failure to register a SPN might cause integrated
    authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered.
    2015-03-24 19:48:52.45 Server      SQL Server is attempting to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a SPN is registered for the SQL Server service. This is an informational
    message. No user action is required.
    2015-03-24 19:48:54.03 Server      The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/AWISCDB.AIRWORKS.IN:SCSMDB ] for the SQL Server service. 
    2015-03-24 19:48:54.03 spid14s     A new instance of the full-text filter daemon host process has been successfully started.
    2015-03-24 19:48:54.86 spid6s      Starting up database 'mssqlsystemresource'.
    2015-03-24 19:48:54.86 spid5s      Starting up database 'msdb'.
    2015-03-24 19:48:54.87 spid6s      The resource database build version is 11.00.3000. This is an informational message only. No user action is required.
    2015-03-24 19:48:55.21 spid5s      12 transactions rolled forward in database 'msdb' (4:0). This is an informational message only. No user action is required.
    2015-03-24 19:48:55.32 spid5s      0 transactions rolled back in database 'msdb' (4:0). This is an informational message only. No user action is required.
    2015-03-24 19:48:55.32 spid6s      Starting up database 'model'.
    2015-03-24 19:48:55.32 spid5s      Recovery is writing a checkpoint in database 'msdb' (4). This is an informational message only. No user action is required.
    2015-03-24 19:48:55.72 spid6s      Clearing tempdb database.
    2015-03-24 19:48:57.22 spid6s      Starting up database 'tempdb'.
    2015-03-24 19:48:59.04 spid5s      Database 'master' is upgrading script 'msdb110_upgrade.sql' from level 184551476 to level 184552376.
    2015-03-24 19:48:59.04 spid5s      ----------------------------------
    2015-03-24 19:48:59.04 spid5s      Starting execution of PRE_MSDB.SQL
    2015-03-24 19:48:59.04 spid5s      ----------------------------------
    2015-03-24 19:49:00.23 spid5s      Setting database option COMPATIBILITY_LEVEL to 100 for database 'msdb'.
    2015-03-24 19:49:00.57 spid5s      -----------------------------------------
    2015-03-24 19:49:00.57 spid5s      Starting execution of PRE_SQLAGENT100.SQL
    2015-03-24 19:49:00.57 spid5s      -----------------------------------------
    2015-03-24 19:49:00.61 spid5s      Setting database option COMPATIBILITY_LEVEL to 110 for database 'msdb'.
    2015-03-24 19:49:00.73 spid5s      Configuration option 'allow updates' changed from 1 to 1. Run the RECONFIGURE statement to install.
    2015-03-24 19:49:00.73 spid5s      Configuration option 'allow updates' changed from 1 to 1. Run the RECONFIGURE statement to install.
    2015-03-24 19:49:01.78 spid5s      Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
    2015-03-24 19:49:01.79 spid5s      Using 'xpstar.dll' version '2011.110.3000' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
    2015-03-24 19:49:01.80 spid5s      DBCC TRACEOFF 1717, server process ID (SPID) 5. This is an informational message only; no user action is required.
    2015-03-24 19:49:01.80 spid5s      DBCC execution completed. If DBCC printed error messages, contact your system administrator.
    2015-03-24 19:49:01.81 spid5s       
    2015-03-24 19:49:01.81 spid5s      Creating table temp_sysjobschedules
    2015-03-24 19:49:01.91 spid5s       
    2015-03-24 19:49:01.91 spid5s      Alter table sysdownloadlist...
    2015-03-24 19:49:01.92 spid5s       
    2015-03-24 19:49:01.92 spid5s      Alter table sysjobhistory...
    2015-03-24 19:49:01.92 spid5s       
    2015-03-24 19:49:01.92 spid5s      Alter table systargetservers...
    2015-03-24 19:49:01.92 spid5s       
    2015-03-24 19:49:01.92 spid5s      Alter table sysjobsteps...
    2015-03-24 19:49:01.99 spid5s      Configuration option 'allow updates' changed from 1 to 0. Run the RECONFIGURE statement to install.
    2015-03-24 19:49:01.99 spid5s      Configuration option 'allow updates' changed from 1 to 0. Run the RECONFIGURE statement to install.
    2015-03-24 19:49:01.99 spid5s       
    2015-03-24 19:49:01.99 spid5s      -----------------------------------------
    2015-03-24 19:49:01.99 spid5s      Execution of PRE_SQLAGENT100.SQL complete
    2015-03-24 19:49:01.99 spid5s      -----------------------------------------
    2015-03-24 19:49:02.01 spid5s      DMF pre-upgrade steps...
    2015-03-24 19:49:02.13 spid5s      DC pre-upgrade steps...
    2015-03-24 19:49:02.13 spid5s      Check if Data collector config table exists...
    2015-03-24 19:49:02.13 spid5s      Data Collector state before upgrade: 0
    2015-03-24 19:49:02.13 spid5s      pre_dc100::Check if syscollector_collection_sets_internal table exists...
    2015-03-24 19:49:02.13 spid5s      pre_dc100::Capturing Collection set status in temp table...
    2015-03-24 19:49:02.19 spid5s      Deleting cached auto-generated T-SQL Data Collection packages from msdb...
    2015-03-24 19:49:02.19 spid5s      End of DC pre-upgrade steps.
    2015-03-24 19:49:02.19 spid5s      DAC pre-upgrade steps...
    2015-03-24 19:49:02.19 spid5s      Starting DAC pre-upgrade steps ...
    2015-03-24 19:49:02.19 spid5s      End of DAC pre-upgrade steps.
    2015-03-24 19:49:02.19 spid5s      ----------------------------------
    2015-03-24 19:49:02.19 spid5s      Starting execution of MSDB.SQL
    2015-03-24 19:49:02.19 spid5s      ----------------------------------
    2015-03-24 19:49:02.23 spid5s      Configuration option 'allow updates' changed from 0 to 1. Run the RECONFIGURE statement to install.
    2015-03-24 19:49:02.23 spid5s      Configuration option 'allow updates' changed from 0 to 1. Run the RECONFIGURE statement to install.
    2015-03-24 19:49:02.27 spid5s      Checking the size of MSDB...
    2015-03-24 19:49:02.53 spid5s       
    2015-03-24 19:49:02.53 spid5s      Setting database option TRUSTWORTHY to ON for database 'msdb'.
    2015-03-24 19:49:02.53 spid5s      Setting database option RECOVERY to SIMPLE for database 'msdb'.
    2015-03-24 19:49:02.64 spid5s      ----------------------------------
    2015-03-24 19:49:02.64 spid5s      Finished execution of MSDB.SQL
    2015-03-24 19:49:02.64 spid5s      ----------------------------------
    2015-03-24 19:49:02.64 spid5s      -----------------------------------------
    2015-03-24 19:49:02.64 spid5s      Starting execution of MSDB_VERSIONING.SQL
    2015-03-24 19:49:02.64 spid5s      -----------------------------------------
    2015-03-24 19:49:02.64 spid5s      -----------------------------------------
    2015-03-24 19:49:02.64 spid5s      Finished execution of MSDB_VERSIONING.SQL
    2015-03-24 19:49:02.64 spid5s      -----------------------------------------
    2015-03-24 19:49:02.64 spid5s      Dropping view MSdatatype_mappings...
    2015-03-24 19:49:02.65 spid5s      Dropping view sysdatatypemappings...
    2015-03-24 19:49:02.65 spid5s      Dropping table MSdbms_datatype_mapping...
    2015-03-24 19:49:02.66 spid5s      Dropping table MSdbms_map...
    2015-03-24 19:49:02.67 spid5s      Dropping table MSdbms_datatype...
    2015-03-24 19:49:02.67 spid5s      Dropping table MSdbms...
    2015-03-24 19:49:02.73 spid5s      Creating table MSdbms
    2015-03-24 19:49:02.75 spid5s      Creating table MSdbms_datatype
    2015-03-24 19:49:03.01 spid5s      Creating table MSdbms_map
    2015-03-24 19:49:03.02 spid5s      Creating table MSdbms_datatype_mapping
    2015-03-24 19:49:03.03 spid5s      Definining default datatype mappings
    2015-03-24 19:49:03.04 spid5s      Creating datatype mappings for MSSQLSERVER to ORACLE8
    2015-03-24 19:49:03.21 spid5s      Creating datatype mappings for MSSQLSERVER to ORACLE9
    2015-03-24 19:49:03.29 spid5s      Creating datatype mappings for MSSQLSERVER to ORACLE10
    2015-03-24 19:49:03.37 spid5s      Creating datatype mappings for MSSQLSERVER to ORACLE11
    2015-03-24 19:49:03.46 spid5s      Creating datatype mappings for MSSQLSERVER to DB2
    2015-03-24 19:49:03.54 spid5s      Creating datatype mappings for MSSQLSERVER to SYBASE
    2015-03-24 19:49:03.62 spid5s      Creating datatype mappings for ORACLE8 to MSSQLSERVER
    2015-03-24 19:49:03.71 spid5s      Creating datatype mappings for ORACLE9 to MSSQLSERVER
    2015-03-24 19:49:03.83 spid5s      Creating datatype mappings for ORACLE10 to MSSQLServer
    2015-03-24 19:49:03.95 spid5s      Creating datatype mappings for ORACLE11 to MSSQLServer
    2015-03-24 19:49:04.08 spid5s      Creating view MSdatatype_mappings
    2015-03-24 19:49:04.08 spid5s      Creating view sysdatatypemappings
    2015-03-24 19:49:05.08 spid5s       
    2015-03-24 19:49:05.08 spid5s      Creating table syssubsystems...
    2015-03-24 19:49:05.09 spid5s       
    2015-03-24 19:49:05.09 spid5s      Creating view sysproxyloginsubsystem_view...
    2015-03-24 19:49:05.11 spid5s       
    2015-03-24 19:49:05.11 spid5s      Creating trigger trig_sysoriginatingservers_delete...
    2015-03-24 19:49:05.11 spid5s       
    2015-03-24 19:49:05.11 spid5s      Creating view sysoriginatingservers_view...
    2015-03-24 19:49:05.12 spid5s       
    2015-03-24 19:49:05.12 spid5s      Creating trigger trig_sysjobs_insert_update...
    2015-03-24 19:49:05.13 spid5s       
    2015-03-24 19:49:05.13 spid5s      Creating view sysjobs_view...
    2015-03-24 19:49:05.15 spid5s       
    2015-03-24 19:49:05.15 spid5s      Creating trigger trig_sysschedules_insert_update...
    2015-03-24 19:49:05.16 spid5s       
    2015-03-24 19:49:05.16 spid5s      Creating view sysschedules_localserver_view...
    2015-03-24 19:49:05.21 spid5s       
    2015-03-24 19:49:05.21 spid5s      Creating view systargetservers_view...
    2015-03-24 19:49:05.23 spid5s       
    2015-03-24 19:49:05.23 spid5s      Creating view sysalerts_performance_counters_view...
    2015-03-24 19:49:05.25 spid5s       
    2015-03-24 19:49:05.25 spid5s      Creating function SQLAGENT_SUSER_SNAME ...
    2015-03-24 19:49:05.25 spid5s       
    2015-03-24 19:49:05.25 spid5s      Creating function SQLAGENT_SUSER_SID ...
    2015-03-24 19:49:05.26 spid5s       
    2015-03-24 19:49:05.26 spid5s      Creating procedure SP_SQLAGENT_IS_SRVROLEMEMBER...
    2015-03-24 19:49:05.27 spid5s       
    2015-03-24 19:49:05.27 spid5s      Creating procedure sp_verify_category_identifiers...
    2015-03-24 19:49:05.27 spid5s       
    2015-03-24 19:49:05.27 spid5s      Creating function agent_datetime...
    2015-03-24 19:49:05.27 spid5s       
    2015-03-24 19:49:05.27 spid5s      Creating procedure sp_verify_proxy_identifiers...
    2015-03-24 19:49:05.28 spid5s       
    2015-03-24 19:49:05.28 spid5s      Creating procedure sp_verify_credential_identifiers...
    2015-03-24 19:49:05.29 spid5s       
    2015-03-24 19:49:05.29 spid5s      Creating procedure sp_verify_subsystems...
    2015-03-24 19:49:05.30 spid5s       
    2015-03-24 19:49:05.30 spid5s      Creating procedure sp_verify_subsystem_identifiers...
    2015-03-24 19:49:05.30 spid5s       
    2015-03-24 19:49:05.30 spid5s      Creating procedure sp_verify_login_identifiers...
    2015-03-24 19:49:05.31 spid5s       
    2015-03-24 19:49:05.31 spid5s      Creating procedure sp_verify_proxy...
    2015-03-24 19:49:05.31 spid5s       
    2015-03-24 19:49:05.31 spid5s      Creating procedure sp_add_proxy...
    2015-03-24 19:49:05.32 spid5s       
    2015-03-24 19:49:05.32 spid5s      Creating procedure sp_delete_proxy...
    2015-03-24 19:49:05.32 spid5s       
    2015-03-24 19:49:05.32 spid5s      Creating procedure sp_update_proxy...
    2015-03-24 19:49:05.33 spid5s       
    2015-03-24 19:49:05.33 spid5s      Creating procedure sp_sqlagent_is_member...
    2015-03-24 19:49:05.33 spid5s       
    2015-03-24 19:49:05.33 spid5s      Creating procedure sp_verify_proxy_permissions...
    2015-03-24 19:49:05.34 spid5s       
    2015-03-24 19:49:05.34 spid5s      Creating procedure sp_help_proxy...
    2015-03-24 19:49:05.35 spid5s       
    2015-03-24 19:49:05.35 spid5s      Creating procedure sp_get_proxy_properties...
    2015-03-24 19:49:05.36 spid5s       
    2015-03-24 19:49:05.36 spid5s      Creating procedure sp_grant_proxy_to_subsystem...
    2015-03-24 19:49:05.36 spid5s       
    2015-03-24 19:49:05.36 spid5s      Creating procedure sp_grant_login_to_proxy...
    2015-03-24 19:49:05.37 spid5s       
    2015-03-24 19:49:05.37 spid5s      Creating procedure sp_revoke_login_from_proxy...
    2015-03-24 19:49:05.37 spid5s       
    2015-03-24 19:49:05.37 spid5s      Creating procedure sp_revoke_proxy_from_subsystem...
    2015-03-24 19:49:05.38 spid5s       
    2015-03-24 19:49:05.38 spid5s      Creating procedure sp_enum_proxy_for_subsystem...
    2015-03-24 19:49:05.38 spid5s       
    2015-03-24 19:49:05.38 spid5s      Creating procedure sp_enum_login_for_proxy...
    2015-03-24 19:49:05.39 spid5s       
    2015-03-24 19:49:05.39 spid5s      Creating procedure sp_reassign_proxy...
    2015-03-24 19:49:05.40 spid5s       
    2015-03-24 19:49:05.40 spid5s      Creating procedure sp_sqlagent_get_startup_info...
    2015-03-24 19:49:05.41 spid5s       
    2015-03-24 19:49:05.41 spid5s      Creating procedure sp_sqlagent_update_agent_xps...
    2015-03-24 19:49:05.42 spid5s       
    2015-03-24 19:49:05.42 spid5s      Creating procedure sp_sqlagent_has_server_access...
    2015-03-24 19:49:05.45 spid5s       
    2015-03-24 19:49:05.45 spid5s      Creating procedure sp_sqlagent_get_perf_counters...
    2015-03-24 19:49:05.46 spid5s       
    2015-03-24 19:49:05.46 spid5s      Creating procedure sp_sqlagent_notify...
    2015-03-24 19:49:05.47 spid5s       
    2015-03-24 19:49:05.47 spid5s      Creating procedure sp_is_sqlagent_starting...
    2015-03-24 19:49:05.47 spid5s       
    2015-03-24 19:49:05.47 spid5s      Creating procedure sp_verify_job_identifiers...
    2015-03-24 19:49:05.48 spid5s       
    2015-03-24 19:49:05.48 spid5s      Creating procedure sp_verify_schedule_identifiers...
    2015-03-24 19:49:05.49 spid5s       
    2015-03-24 19:49:05.49 spid5s      Creating procedure sp_verify_jobproc_caller...
    2015-03-24 19:49:05.50 spid5s       
    2015-03-24 19:49:05.50 spid5s      Creating procedure sp_downloaded_row_limiter...
    2015-03-24 19:49:05.51 spid5s       
    2015-03-24 19:49:05.51 spid5s      Creating procedure sp_post_msx_operation...
    2015-03-24 19:49:05.54 spid5s       
    2015-03-24 19:49:05.54 spid5s      Creating procedure sp_verify_performance_condition...
    2015-03-24 19:49:05.58 spid5s       
    2015-03-24 19:49:05.58 spid5s      Creating procedure sp_verify_job_date...
    2015-03-24 19:49:05.59 spid5s       
    2015-03-24 19:49:05.59 spid5s      Creating procedure sp_verify_job_time...
    2015-03-24 19:49:05.61 spid5s       
    2015-03-24 19:49:05.61 spid5s      Creating procedure sp_verify_alert...
    2015-03-24 19:49:05.62 spid5s       
    2015-03-24 19:49:05.62 spid5s      Creating procedure sp_update_alert...
    2015-03-24 19:49:05.63 spid5s       
    2015-03-24 19:49:05.63 spid5s      Creating procedure sp_delete_job_references...
    2015-03-24 19:49:05.65 spid5s       
    2015-03-24 19:49:05.65 spid5s      Creating procedure sp_delete_all_msx_jobs...
    2015-03-24 19:49:05.66 spid5s       
    2015-03-24 19:49:05.66 spid5s      Creating procedure sp_generate_target_server_job_assignment_sql...
    2015-03-24 19:49:05.66 spid5s       
    2015-03-24 19:49:05.66 spid5s      Creating procedure sp_generate_server_description...
    2015-03-24 19:49:05.67 spid5s       
    2015-03-24 19:49:05.67 spid5s      Creating procedure sp_msx_set_account...
    2015-03-24 19:49:05.68 spid5s       
    2015-03-24 19:49:05.68 spid5s      Creating procedure sp_msx_get_account...
    2015-03-24 19:49:05.69 spid5s       
    2015-03-24 19:49:05.69 spid5s      Creating procedure sp_delete_operator...
    2015-03-24 19:49:05.70 spid5s       
    2015-03-24 19:49:05.70 spid5s      Creating procedure sp_msx_defect...
    2015-03-24 19:49:05.71 spid5s       
    2015-03-24 19:49:05.71 spid5s      Creating procedure sp_msx_enlist...
    2015-03-24 19:49:05.72 spid5s       
    2015-03-24 19:49:05.72 spid5s      Creating procedure sp_delete_targetserver...
    2015-03-24 19:49:05.73 spid5s       
    2015-03-24 19:49:05.73 spid5s      Creating procedure sp_enlist_tsx
    2015-03-24 19:49:05.74 spid5s       
    2015-03-24 19:49:05.74 spid5s      Creating procedure sp_get_sqlagent_properties...
    2015-03-24 19:49:05.76 spid5s       
    2015-03-24 19:49:05.76 spid5s      Create procedure sp_set_sqlagent_properties...
    2015-03-24 19:49:05.76 spid5s       
    2015-03-24 19:49:05.76 spid5s      Creating procedure sp_add_targetservergroup...
    2015-03-24 19:49:05.77 spid5s       
    2015-03-24 19:49:05.77 spid5s      Creating procedure sp_update_targetservergroup...
    2015-03-24 19:49:05.78 spid5s       
    2015-03-24 19:49:05.78 spid5s      Creating procedure sp_delete_targetservergroup...
    2015-03-24 19:49:05.78 spid5s       
    2015-03-24 19:49:05.78 spid5s      Creating procedure sp_help_targetservergroup...
    2015-03-24 19:49:05.79 spid5s       
    2015-03-24 19:49:05.79 spid5s      Creating procedure sp_add_targetsvgrp_member...
    2015-03-24 19:49:05.80 spid5s       
    2015-03-24 19:49:05.80 spid5s      Creating procedure sp_delete_targetsvrgrp_member...
    2015-03-24 19:49:05.81 spid5s       
    2015-03-24 19:49:05.81 spid5s      Creating procedure sp_verify_category...
    2015-03-24 19:49:05.81 spid5s       
    2015-03-24 19:49:05.81 spid5s      Creating procedure sp_add_category...
    2015-03-24 19:49:05.82 spid5s       
    2015-03-24 19:49:05.82 spid5s      Creating procedure sp_update_category...
    2015-03-24 19:49:05.83 spid5s       
    2015-03-24 19:49:05.83 spid5s      Creating procedure sp_delete_category...
    2015-03-24 19:49:05.83 spid5s       
    2015-03-24 19:49:05.84 spid5s      Creating procedure sp_help_category...
    2015-03-24 19:49:05.84 spid5s       
    2015-03-24 19:49:05.84 spid5s      Creating procedure sp_help_targetserver...
    2015-03-24 19:49:05.85 spid5s       
    2015-03-24 19:49:05.85 spid5s      Creating procedure sp_resync_targetserver...
    2015-03-24 19:49:06.06 spid5s       
    2015-03-24 19:49:06.06 spid5s      Creating procedure sp_purge_jobhistory...
    2015-03-24 19:49:06.09 spid5s       
    2015-03-24 19:49:06.09 spid5s      Creating procedure sp_help_jobhistory...
    2015-03-24 19:49:06.10 spid5s       
    2015-03-24 19:49:06.10 spid5s      Creating procedure sp_add_jobserver...
    2015-03-24 19:49:06.11 spid5s       
    2015-03-24 19:49:06.11 spid5s      Creating procedure sp_delete_jobserver...
    2015-03-24 19:49:06.11 spid5s      Error: 10011, Severity: 16, State: 1.
    2015-03-24 19:49:06.11 spid5s      Access denied.
    2015-03-24 19:49:06.11 spid5s      Error: 917, Severity: 15, State: 1.
    2015-03-24 19:49:06.11 spid5s      An upgrade script batch failed to execute for database 'master' due to compilation error. Check the previous error message  for the line which caused compilation to fail.
    2015-03-24 19:49:06.11 spid5s      Error: 912, Severity: 21, State: 2.
    2015-03-24 19:49:06.11 spid5s      Script level upgrade for database 'master' failed because upgrade step 'msdb110_upgrade.sql' encountered error 917, state 1, severity 15. This is a serious error condition which might interfere with regular
    operation and the database will be taken offline. If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective
    actions and re-start the database so that the script upgrade steps run to completion.
    2015-03-24 19:49:06.11 spid5s      Error: 3417, Severity: 21, State: 3.
    2015-03-24 19:49:06.11 spid5s      Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books
    Online.
    2015-03-24 19:49:06.12 spid5s      SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
    2015-03-24 19:49:06.50 spid12s     The SQL Server Network Interface library successfully deregistered the Service Principal Name (SPN) [ MSSQLSvc/AWISCDB.AIRWORKS.IN:SCSMDB ] for the SQL Server service. 
    Shailendra Dev

  • Named Instance in SQL Server 2000

    We recently switched to SQL Server 2000 and are now having some
    problems. Our SQL Farm set up named instances so we could take
    advantage of active/active clustering. In doing this, they set up 2
    Named Instances, and therefore both cluster nodes are identically
    configured. To avoid a single point of failure, we'd like to take
    advantage of the active/active clustering when we call into the SQL
    Server 2000 database and not have to specify the exact port of either
    instance.
    Based on some information from a colleuge that is familiar with
    accessing SQL Server from the MicroSoft environment, we should be able
    to specify server=servername\instance:1434. This in turn would
    determine the correct port for one of the instances and the driver
    should handle forwarding our request to that instance.
    Does the WebLogic driver handle this? If so, does anyone know the
    proper syntax for the connection string?

    Hi. Our driver will only connect to a DBMS by being given it's
    machine name and port. If there are two DBMSes on the one machine,
    then they will be distinguished (only) by different port numbers.
    Our driver will not automatically switch from one port to another.
    Joe Weinstein
    Julie Burnard wrote:
    >
    We recently switched to SQL Server 2000 and are now having some
    problems. Our SQL Farm set up named instances so we could take
    advantage of active/active clustering. In doing this, they set up 2
    Named Instances, and therefore both cluster nodes are identically
    configured. To avoid a single point of failure, we'd like to take
    advantage of the active/active clustering when we call into the SQL
    Server 2000 database and not have to specify the exact port of either
    instance.
    Based on some information from a colleuge that is familiar with
    accessing SQL Server from the MicroSoft environment, we should be able
    to specify server=servername\instance:1434. This in turn would
    determine the correct port for one of the instances and the driver
    should handle forwarding our request to that instance.
    Does the WebLogic driver handle this? If so, does anyone know the
    proper syntax for the connection string?--
    B.E.A. is now hiring! (12/14/01) If interested send a resume to [email protected]
    DIRECTOR OF PRODUCT PLANS AND STRATEGY San Francisco, CA
    E-SALES BUSINESS DEVELOPMENT REPRESENTATIVE Dallas, TX
    SOFTWARE ENGINEER (DBA) Liberty Corner, NJ
    SENIOR WEB DEVELOPER San Jose, CA
    SOFTWARE ENGINEER (ALL LEVELS), CARY, NORTH CAROLINA San Jose, CA
    SR. PRODUCT MANAGER Bellevue, WA
    SR. WEB DESIGNER San Jose, CA
    Channel Marketing Manager - EMEA Region London, GBR
    DIRECTOR OF MARKETING STRATEGY, APPLICATION SERVERS San Jose, CA
    SENIOR SOFTWARE ENGINEER (PLATFORM) San Jose, CA
    E-COMMERCE INTEGRATION ARCHITECT San Jose, CA
    QUALITY ASSURANCE ENGINEER Redmond, WA
    Services Development Manager (Business Development Manager - Services) Paris, FRA; Munich, DEU
    SENIOR SOFTWARE ENGINEER (PLATFORM) Redmond, WA
    E-Marketing Programs Specialist EMEA London, GBR
    BUSINESS DEVELOPMENT DIRECTOR - E COMMERCE INTEGRATION San Jose, CA
    MANAGER, E-SALES Plano, TX

  • SSAS 2012 (SP2) - Connecting to a Named Instance in a Failover Cluster

    I posted this question some months ago and never got a resolution...still having the same problem. (http://social.msdn.microsoft.com/Forums/sqlserver/en-US/4178ba62-87e2-4672-a4ef-acd970ac1011/ssas-2012-sp1-connecting-to-a-named-instance-in-a-failover-cluster?forum=sqlanalysisservices)
    I have a 3 node failover cluster installation (active-passive-passive) configured as follows:
    Node1: DB Engine 1 (named instance DB01)
    Node2: DB Engine 2 (named instance DB02)
    Node3: Analysis Services (named instance DBAS)
    Obviously, the node indicated is merely the default active node for each service, with each service able to fail from node to node as required.
    Strangely, when I attempt to connect to the SSAS node using the cluster netbios "alias" (dunno, what else it would be called, so I apologize if I am mixing terminology or somesuch), I am only able to do so by specifying the the alias _without_ the
    required named instance. If I issue a connection request using an external program or even SSMS using Node3\DBAS or Node3.domain\DBAS, it appears that the SQL Server Browser is offering up a bogus TCP port for the named instance (in my case TCP/58554), when
    in reality, the SSAS service is running on TCP/2383 (confirmed with netstat) -- which if I understand correctly after much, much reading on the subject is the only port that can be used in a failover cluster. In any case, I'm puzzled beyond words. As I think
    through it, I believe I've seen this issue in the past, but never worried about it since it wasn't necessary to specify the named instance when I had SSAS requirements... It's only a showstopper now because I'm finalizing my implementation of SCVMM/SCOM 2012
    R2, and for some strange reason the PRO configuration in VMM gets all butthurt if you don't offer up a named instance...
    Thank you much for reading. I appreciate any help to get this resolved.
    POSSIBLY NOT RELEVANT...?
    I've properly configured the SPNs for the SSAS service (MSOLAPSvc.3) and the SQL Browser (MSOLAPDisco.3), with the former mapped to the SSAS service account and the latter to the cluster "alias" (since it runs as "NT AUTHORITY\LOCALSERVICE"
    as is customary) and have permitted delegation on the service and machine accounts as required. So, I'm not getting any kerberos issues with the service...any more, that is... ;) I'm not sure that's important, but I wanted to be forthcoming with details to
    help solve the issue.

    When connecting to SSAS in a cluster, you do not specify an instance name.  In your case, you would use the name of the SSAS IP address to connect.
    See:
    http://msdn.microsoft.com/en-us/library/dn141153.aspx
    For servers deployed in a failover cluster, connect using the network name of the SSAS cluster. This name is specified during SQL Server setup, as
    SQL Server Network Name. Note that if you installed SSAS as a named instance onto a Windows Server Failover Cluster (WSFC), you never add the instance name on the connection. This practice is unique to SSAS; in contrast, a named
    instance of a clustered relational database engine does include the instance name. For example, if you installed both SSAS and the database engine as named instance (Contoso-Accounting) with a SQL Server Network Name of SQL-CLU, you would connect to SSAS using
    "SQL-CLU" and to the database engine as "SQL-CLU\Contoso-Accounting". See
    How to Cluster SQL Server Analysis Services for more information and examples.

  • Sql server 2012 express - tcp/ip connection to named instance using dynamic port not working

    I have a named instance on a SQL 2012 Express server that won't connect via TCP/IP when wanting to connect off of the dynamic port.  I can connect via shared memory locally on the server.   I can connect to the namespace when specifying the
    dynamic port listed in the configuration manager.  
    This is the only named instance on the server and it is not the default.
    TCP/IP is enabled
    Allow Remote connections is enabled
    the server browser service is running
    I can connect via the dynamic port number
    I am testing the connection locally on the server, so I don't believe a firewall is the issue.  I get the same results if I test it from a remote computer.
    When using the sqlcmd (sqlcmd -S tcp:SQLSRVR\NAMEINST -E) I get the message that "the requested protocol isn't supported [xfffffffff]".   The command (sqlcmd -S tcp:SQLSRVR\NAMEINST,59992 -E) works.
    Through SSMS, I get the message "the connection was actively refused".
    On other boxes, I can connect with the named instance without having to specify the port. 
    I have looked through the sql logs and nothing much shows up.  The log does show that is listening on the port # for ipv4 and ipv6.   There is also a line in there talking about the SPN not being registered and not to worry about it if
    you are not using Kerberos.  I logged in through shared memory and it said I was using NTLM.
    Any help would be appreciated.
    thanks.

    Hi clw,
    I’m writing to follow up with you on this post. According to your description, I do a test, if you configure the database engine to listen on a specific TCP port (59992), and
    the port is opened in the firewall. If you want to connect to the SQL Server instance, you 'd better to
    use the port number.
    In my opinion, by default, the default instance of the Database Engine uses port 1433, usually, if you have configured the server to listen on a non-default port number, when an instance of SQL Server uses dynamic port allocation, the connection string that
    is built at the SQL Server client does not specify the destination TCP/IP port unless the user or the programmer explicitly specifies the port. Therefore, the SQL Server client library queries the server on UDP port 1434 to collect the information about the
    destination instance of SQL Server.
    If UDP port 1434 is disabled, the SQL Server client cannot dynamically determine the port of the named instance of SQL Server. Therefore, the SQL Server client may be unable to connect to the named instance of SQL Server. In this situation, the SQL Server
    client must specify the dynamically allocated port where the named instance of SQL Server is listening.
    For more information about configuring an instance of SQL Server to listen on a specific TCP port or dynamic port, you can review the following article.
    https://support.transfrm.com/entries/503111-How-to-configure-an-instance-of-SQL-Server-to-listen-on-a-specific-TCP-port-or-dynamic-port
    Thanks,
    Sofiya Li
    Sofiya Li
    TechNet Community Support

  • How to know if an insance is a default instance or a named instance?

    I obtain a list of instance names by using the method in this article:
    http://blogs.msdn.com/b/askjay/archive/2011/10/11/how-can-i-get-a-list-of-installed-sql-server-instances.aspx
    On my computer, there are two instance names under registry key:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\SQL
    That is:
    SQLEXPRESS   
    MSSQLSERVER
    Then how to know whether the above two instances are both named instance or one of them is default instance?
    Thanks

    I obtain a list of instance names by using the method in this article:
    http://blogs.msdn.com/b/askjay/archive/2011/10/11/how-can-i-get-a-list-of-installed-sql-server-instances.aspx
    On my computer, there are two instance names under registry key:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\SQL
    That is:
    SQLEXPRESS   
    MSSQLSERVER
    Then how to know whether the above two instances are both named instance or one of them is default instance?
    Thanks
    Hi,
    Generally when you don't give name to SQL server instance or select default instance during installation  it takes MSSQLSERVER as a default name so where ever you see MSSQLSERVER its always default instance. SQLEXPRESS will be SQL express instance(
    although you can rename it) all other instances would be named accordingly. SO MSSQLSERVER is default instance all other which appear will be named instances
    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
    My TechNet Wiki Articles

  • SQL Server 2000 and Named Instances

    Heya,
    I'm having trouble creating a JDBC Connection Pool against our SQL Server box through the Admin Console. There are firewalls between the Weblogic box and the SQL Box, and they have traffic blocked on port 1434. I am specifying port 1433 in the URL, but it seems that it's still trying to do the dynamic port determination through UDP on 1434. My URL is along the lines of:
    jdbc:bea:sqlserver://99.99.99.99\\MYINSTANCE:1433
    Is there a way with named instances to force the driver to use the indicated port? I'm going to see if they'll open up port 1434 for a test, but I wanted to know if there are other options.
    Thanks,
    Anna

    Anna Veirauchs wrote:
    Heya,
    I gave it a try and it threw a socket error: Unknown host 99.99.99.99/myinstance
    I've been researching the issue on my end and I think I might be able to treat it like a non-named instance. This was sort-of hinted at in some Microsoft documentation for their JDBC driver. On Weblogic I put it in as 99.99.99.99 instead of 99.99.99.99\\myinstance and I got a connection. I'm confirming with my DBA that it somehow connected to the right database. It could be that since they've set up SQL Server with static ports it doesn't need the instance name. In SQL Server, you can't use dynamic p
    ort discovery if your database is not a member of a named instance, so the JDBC is forced to use the port you specify. Most people use dynamic discovery with named instances, but probably for security reasons our DBA does not want to use it.
    I really appreciate you taking time to look into this for me!
    Thanks,
    Anna
    P.S. That Admin Console does have another problem when setting up pools with named instances.
    You put it in as 99.99.99.99\\myinstance, the test will connect correctly, but when you try
    to create and deploy to a server you get an error because it appears to write 99.99.99.99myinstance somewhere.
    You usually have to go back to the Properties attribute and reinsert the "\\" for it to work right.you're very welcome. I will file a change request about the double back-slash...
    Joe

  • MS SQL 2008 R2 Named instance: Login failed. Microsoft SQL server, Error: 18452) - Tryig to access using the FQDN assigned for the backup network card.

    Hi,
       I have a windows 2008 R2 Enterprise servers with standalone MS-SQL 2008 R2 named instance.  The server is having two networks, once production and the second for backup. The server FQDN is resolving to the production IP. The backup NIC
    DNS dynamic update is disabled and an "A" record is registered with the dns.  While trying to connect to the instance using the management studio:
    Successfuly able to connect using the instance name, the production hostname, production IP and backup IP. 
    but while trying to connect to the insance using the backup hostname getting the below error:
    "Login failed. The login is an untrusted domain and cannot be used with windows authentication. (Microsoft SQL server, Error: 18452) "
    This is required for the backup tool to get connected using the backup FQDN of the server.
    Should I need to create a host name alias,  request you to kindly assist me with the best recommedation to fix this.
    http://blogs.msdn.com/b/dbrowne/archive/2012/05/21/how-to-add-a-hostname-alias-for-a-sql-server-instance.aspx

    Hi,
    It might be a kerberos issue.  Check that there are valid SPN's registered using the setspn utility - http://technet.microsoft.com/en-us/library/cc731241.aspx
    Thanks, Andrew
    My blog...

  • DI Server - Cannot connect to named instance SQL server database

    Hi,
    I have developed a small DI server application and want to migrate it to a production server. I keep on getting the Cannot connect to SBOCommon error on login though. I have verified all user names and passwords and the only real difference is that the production environment uses a named instance SQL server eg server\instance setup.
    The production DI server will however connect perfectly to the test database (which is NOT a named instance) .
    Anyone using DI server against a named instance SQL server or have some other ideas what might cause this?
    I use B1WS 1.0 and the version of SBO is 8.00.181..
    Jaco

    I may have solved the problem, at least partially.
    I created a test user with full rights on my test database server and it would also not connect, even though my test database is not a an instance setup.
    Then I found this thread  [Re: DI Server Always Uses SA to log into MS SQL database even if SOAP packet]
    It seems that at my current patch level the user 'sa' is hard coded into the DI server as sql username! I don't have the production server's 'sa' user credentials at present but will test it on Monday. Will also test against 8.8 soon ..

Maybe you are looking for

  • IOS5.0.1 Bluetooth does not work existing equipment you need to check which type of headset/handsfree kit work

    I have just upgrade to the 4S and at the same time it has has IOS5.0.1 upgrade before using the phone. I find that teh latest version of blue tooth does not with handsfree/headsets I have. I now have to find out if it will work. Apples view is they h

  • New window not appearing

    While working on Oracle Discoverer. When the user opens a report and clicks on the search button a new window should appear but it doesn't.

  • Invoice posting through SUS

    Dear Team, We are implementing MM SUS scenario, currently we are using SRM 5.0 with ECC 6.0 as backend. We understand that the invoice submission by Vendor in SUS, will post invoice in ECC. However, we are looking for option of Parking the invoice in

  • Return PO Process

    Hi Friends, In which scenario we can make use of Return PO process(Me21Nà MIGO) compared with normal reversal process (MBST or MBRL), Thanks and regrads, Chalaa,

  • How To: Enter non-time referenced event, eg, a birthday, etc.

    I am finally beginning to use the Calendar on the iPhone (longtime Palm user). How do you enter something like a recurring birthday or an event/reminder that is not "time related?" Many thanks.