SQL Server Plugin - Remote Connections to Monitor Targets

Hi,
We have OEM 10.2.0.4.0 on MS Windows Server 2003 Service Pack 1. Trying to configure SQL Server Plugin Release 6 (microsoft_sqlserver_database version 3.2.3.1.0). No issues monitoring SQL Server 2005 SP2 installed on same box the Grid. Next test - monitoring SQL Server 2005 SP2 installed on a remote box H2UA62218F7.ad2.prod, tcpip port 4334. On "Add Microsoft SQL Server" screen:
Add Microsoft SQL Server
Properties
* Name
Type Microsoft SQL Server
Name Value
JDBC URL (Example : jdbc:sqlserver://<host>:<port>) jdbs:sqlserver://H2UA62218F7.ad2.prod:4334
JDBC Driver (Optional) com.microsoft.sqlserver.jdbc.SQLServerDriver
Database Username sa
Password of Database User sa_password
System Username (Needed when SQLServer is at remote location) domain_user_with_admin_privs_to_sql_server_box
System Password (Needed when SQLServer is at remote location) domain_user_password
Role (Optional)
The following errors are returned when testing connection:
MSSQLInstance_TestMetric_DynamicProperty - Failed to connect, reason : No suitable driver
MSSQLExistence_TestMetric - Missing Properties : [STDINWBEM_HOST,servername_from_jdbc]
OSType_TargetHost_DynamicProperty - Missing Properties : [STDINWBEM_HOST] 
 
Event Viewer on remote box does not show any login attempts. I am confused why it can not find same jdbs driver it finds to monitor local SQL Server 2005 instance? It should look in same %Agent_Home%\sysman\config\classpath.lst and should see same entry C:\OracleHomes\agent10g\sysman\jdbcdriver\sqljdbc_1.2\enu\sqljdbc.jar. Any thoughts?
 
 
Thanks,
 
 
SY.

Metric "Space Available %" in Metric and Policy Setting page has default warning threshold of 20% and critical threshold of 10%. You can change this, as required.

Similar Messages

SQL Server Express Remote Connection is an Official Function or Not

There are lots of guide on internet about this topic or in the forum.
And I have already tested SQL Server 2008 R2 Express Remote Connection successfully, for usage of an application server.
But I am not sure about this function is Ok or not for production environment, as someone said Remote Connection with SQL Express is not an official function and not supported by Microsoft. Is it true?
Is there some white paper or official function spec about SQL Express to clarify it?

Sure it's an official function of the SQL Server Express Edition.
By default it's only disabled by security reasons, because in common the Express Edition is used for smaller applications running on one machine.
Olaf Helper
[ Blog] [ Xing] [ MVP]

Could not connect to SQL Server 2012 Remotely

Hello,
I have a situation as follows:
The Server
SQL Server 2012 Standard Edition installed on Windows Server 2012 Standard Edition
Active Directory is installed on the same server as well
Remote Access Role added and configured to connect VPN
DNS Role added
Windows Firewall is disabled
The Server is connected to the internet
SQL Server Service & SQL Browser both are running under domain accounts
SQL Server allows remote connections
The Router
The router that connects the server to the Internet is configured to:
Enable VPN Tunnels Protocols (PPTP, L2TP and IPSec)
Forwarding > Virtual Servers (all requests on TCP and UDP on all ports to the server local IP)
The Client
PC running Windows 7 SP1 with SQL Server 2012 Express
Joined AD on the server
Connected to the internet
VPN Connected to the Server
Can Remote Desktop the Server
Can ping the server host name
Can nslookup the server host name
The Problem
If Both the Server and the Client are connected in the same Local Area Network, Client can connect to the SQL Serve
Once the Client is placed in different location connected to the Interent, VPN connected as described above, I could not connect to the Server using:
Windows Authentication Domain Users or
SQL Server users
and the error message is:
Cannot connect to SERVER\SQLINSTANCE.
ADDITIONAL INFORMATION:
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)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&EvtSrc=MSSQLServer&EvtID=-1&LinkId=20476
Any thoughts
Thanks in advance

Hello Hilary,
I have been working on a small replication test.
On the Publisher, things went smooth and the Snapshot Agent was able to work and produce a snapshot written in a shared folder located on the Publisher
On the Subscriber, as I am testing from SQL Server Express, I had run the following command:
replmerg.exe -Publisher [SERVER\SQLInstance] -PublisherDB [dbRepl] -PublisherSecurityMode 0 -PublisherLogin rplMergeAgent -PublisherPassword p@ssw0rd -Publication [TEST Publication] -Distributor [SERVER\SQLInstance] -DistributorSecurityMode 0 -DistributorLogin
rplMergeAgent -DistributorPassword p@ssw0rd -Subscriber [SUBSCRIBER\SQLInstance] -SubscriberSecurityMode 0 -SubscriberLogin rplMergeAgent -SubscriberPassword p@ssw0rd -SubscriberDB [dbRepl] -SubscriptionType 1 -OutputVerboseLevel 2 -Output C:\TEMP\mergeagent.log
Where
SERVER
Publisher and Distributor
dbRepl
Database to replicate
Merge Agent
rplMergeAgent
Subscriber
SUBSCRIBER
dbRepl
Subscriber Database
Merge Agent
rplMergeAgent
Password
p@ssw0rd
rplMergeAgent
SQL Login defined in both Publisher and Subscriber with same password
Granted the following at Publisher:
Login to Publication Database (dbRepl)
Login to Distribution Database (distribution)
Member of PAL
Granted the following at Subscriber:
db_owner fixed database role in Subscription database (dbRepl)
I couldn't grant rplMergeAgent Read Permission on SnapshotFolder as it is only a SQL Login.
When I ran the above command line, I received the following error:
Message: The schema script 'Person_2.sch' could not be propagated to the subscriber.
I am pasting below the whole log file written by the above command:
2014-04-11 15:38:07.205 Microsoft SQL Server Merge Agent 11.0.2218.0
2014-04-11 15:38:07.342 Copyright (c) 2008 Microsoft Corporation
2014-04-11 15:38:07.389
2014-04-11 15:38:07.406 The timestamps prepended to the output lines are expressed in terms of UTC time.
2014-04-11 15:38:07.433 User-specified agent parameter values:
-Publisher SERVER\SQLInstance
-PublisherDB dbRepl
-PublisherSecurityMode 0
-PublisherLogin rplMergeAgent
-PublisherPassword **********
-Publication TEST Publication
-Distributor SERVER\SQLInstance
-DistributorSecurityMode 0
-DistributorLogin rplMergeAgent
-DistributorPassword **********
-Subscriber SUBSCRIBER\SQLInstance
-SubscriberSecurityMode 0
-SubscriberLogin rplMergeAgent
-SubscriberPassword **********
-SubscriberDB dbRepl
-SubscriptionType 1
-OutputVerboseLevel 2
-Output C:\TEMP\mergeagent.log
2014-04-11 15:38:07.497 Percent Complete: 0
2014-04-11 15:38:07.517 Connecting to Subscriber 'SUBSCRIBER\SQLInstance'
2014-04-11 15:38:07.518 Connecting to OLE DB Subscriber at datasource: 'SUBSCRIBER\SQLInstance', location: '', catalog: 'dbRepl', providerstring: '' using provider 'SQLNCLI11'
2014-04-11 15:38:07.608 OLE DB Subscriber: SUBSCRIBER\SQLInstance
DBMS: Microsoft SQL Server
Version: 10.50.4000
catalog name: dbRepl
user name: rplMergeAgent
API conformance: 0
SQL conformance: 0
transaction capable: 1
read only: F
identifier quote char: "
non_nullable_columns: 0
owner usage: 15
max table name len: 128
max column name len: 128
need long data len:
max columns in table: 1000
max columns in index: 16
max char literal len: 131072
max statement len: 131072
max row size: 131072
2014-04-11 15:38:07.613 OLE DB Subscriber 'SUBSCRIBER\SQLInstance': select SERVERPROPERTY ('ProductVersion')
2014-04-11 15:38:07.617 OLE DB Subscriber 'SUBSCRIBER\SQLInstance': set nocount on declare @dbname sysname select @dbname = db_name() declare @collation nvarchar(255) select @collation = convert(nvarchar(255), databasepropertyex(@dbname, N'COLLATION')) select
collationproperty(@collation, N'CODEPAGE') as 'CodePage', collationproperty(@collation, N'LCID') as 'LCID', collationproperty(@collation, N'COMPARISONSTYLE') as 'ComparisonStyle',cast(case when convert (int,databasepropertyex (@dbname,'comparisonstyle')) &
0x1 = 0x1 then 0 else 1 end as bit) as DB_CaseSensitive,cast(case when convert (int,serverproperty ('comparisonstyle')) & 0x1 = 0x1 then 0 else 1 end as bit) as Server_CaseSensitive set nocount off
2014-04-11 15:38:07.637 OLE DB Subscriber 'SUBSCRIBER\SQLInstance': {?=call sp_helpsubscription_properties (N'SERVER\SQLInstance', N'dbRepl', N'TEST Publication')}
2014-04-11 15:38:07.681 Distributor security mode: 0, login name: rplMergeAgent, password: ********.
2014-04-11 15:38:07.682 Percent Complete: 0
2014-04-11 15:38:07.683 Connecting to Distributor 'SERVER\SQLInstance'
2014-04-11 15:38:07.684 Connecting to OLE DB Distributor at datasource: 'SERVER\SQLInstance', location: '', catalog: '', providerstring: '' using provider 'SQLNCLI11'
2014-04-11 15:38:25.062 OLE DB Distributor: SERVER\SQLInstance
DBMS: Microsoft SQL Server
Version: 11.00.2100
catalog name:
user name: guest
API conformance: 0
SQL conformance: 0
transaction capable: 1
read only: F
identifier quote char: "
non_nullable_columns: 0
owner usage: 15
max table name len: 128
max column name len: 128
need long data len:
max columns in table: 1000
max columns in index: 16
max char literal len: 131072
max statement len: 131072
max row size: 131072
2014-04-11 15:38:28.887 OLE DB Distributor 'SERVER\SQLInstance': select SERVERPROPERTY ('ProductVersion')
2014-04-11 15:38:29.842 OLE DB Distributor 'SERVER\SQLInstance': {call sp_helpdistpublisher (N'SERVER\SQLInstance') }
2014-04-11 15:38:32.198 OLE DB Distributor 'SERVER\SQLInstance': select datasource, srvid from master..sysservers where upper(srvname) = upper(N'SERVER\SQLInstance')
2014-04-11 15:38:33.199 OLE DB Distributor 'SERVER\SQLInstance': {call sp_MShelp_merge_agentid (0,N'dbRepl',N'TEST Publication',null,N'dbRepl',100,N'SUBSCRIBER\SQLInstance')}
2014-04-11 15:38:34.451 OLE DB Subscriber 'SUBSCRIBER\SQLInstance': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2014-04-11 15:38:34.560 OLE DB Distributor 'SERVER\SQLInstance': {call sp_MShelp_profile (23, 4, N'')}
2014-04-11 15:38:36.189 OLE DB Subscriber 'SUBSCRIBER\SQLInstance': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2014-04-11 15:38:36.499 OLE DB Distributor 'SERVER\SQLInstance': {call sys.sp_get_redirected_publisher(N'SERVER\SQLInstance',N'dbRepl',0)}
2014-04-11 15:38:37.396 Percent Complete: 0
2014-04-11 15:38:37.396 OLE DB Subscriber 'SUBSCRIBER\SQLInstance': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2014-04-11 15:38:37.399 Initializing
2014-04-11 15:38:37.401 OLE DB Distributor 'SERVER\SQLInstance': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2014-04-11 15:38:37.403 Connecting to OLE DB Publisher at datasource: 'SERVER\SQLInstance', location: '', catalog: 'dbRepl', providerstring: '' using provider 'SQLNCLI11'
2014-04-11 15:38:38.427 Percent Complete: 0
2014-04-11 15:38:38.428 Validating publisher
2014-04-11 15:38:38.429 OLE DB Distributor 'SERVER\SQLInstance': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2014-04-11 15:38:39.455 Percent Complete: 0
2014-04-11 15:38:39.456 Connecting to Publisher 'SERVER\SQLInstance'
2014-04-11 15:38:39.457 OLE DB Distributor 'SERVER\SQLInstance': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2014-04-11 15:38:46.548 OLE DB Publisher: SERVER\SQLInstance
DBMS: Microsoft SQL Server
Version: 11.00.2100
catalog name: dbRepl
user name: rplMergeAgent
API conformance: 0
SQL conformance: 0
transaction capable: 1
read only: F
identifier quote char: "
non_nullable_columns: 0
owner usage: 15
max table name len: 128
max column name len: 128
need long data len:
max columns in table: 1000
max columns in index: 16
max char literal len: 131072
max statement len: 131072
max row size: 131072
2014-04-11 15:38:50.282 OLE DB Publisher 'SERVER\SQLInstance': set nocount on declare @dbname sysname select @dbname = db_name() declare @collation nvarchar(255) select @collation = convert(nvarchar(255), databasepropertyex(@dbname, N'COLLATION')) select collationproperty(@collation,
N'CODEPAGE') as 'CodePage', collationproperty(@collation, N'LCID') as 'LCID', collationproperty(@collation, N'COMPARISONSTYLE') as 'ComparisonStyle',cast(case when convert (int,databasepropertyex (@dbname,'comparisonstyle')) & 0x1 = 0x1 then 0 else 1 end
as bit) as DB_CaseSensitive,cast(case when convert (int,serverproperty ('comparisonstyle')) & 0x1 = 0x1 then 0 else 1 end as bit) as Server_CaseSensitive set nocount off
2014-04-11 15:38:57.393 OLE DB Publisher 'SERVER\SQLInstance': select SERVERPROPERTY ('ProductVersion')
2014-04-11 15:38:59.236 Connecting to OLE DB Publisher at datasource: 'SERVER\SQLInstance', location: '', catalog: 'dbRepl', providerstring: '' using provider 'SQLNCLI11'
2014-04-11 15:39:07.271 OLE DB Publisher: SERVER\SQLInstance
DBMS: Microsoft SQL Server
Version: 11.00.2100
catalog name: dbRepl
user name: rplMergeAgent
API conformance: 0
SQL conformance: 0
transaction capable: 1
read only: F
identifier quote char: "
non_nullable_columns: 0
owner usage: 15
max table name len: 128
max column name len: 128
need long data len:
max columns in table: 1000
max columns in index: 16
max char literal len: 131072
max statement len: 131072
max row size: 131072
2014-04-11 15:39:45.229 OLE DB Subscriber 'SUBSCRIBER\SQLInstance': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2014-04-11 15:39:45.234 Percent Complete: 0
2014-04-11 15:39:45.235 OLE DB Subscriber 'SUBSCRIBER\SQLInstance': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2014-04-11 15:39:45.236 Retrieving publication information
2014-04-11 15:39:45.238 OLE DB Distributor 'SERVER\SQLInstance': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2014-04-11 15:39:46.287 Percent Complete: 0
2014-04-11 15:39:46.288 Retrieving subscription information.
2014-04-11 15:39:46.290 OLE DB Distributor 'SERVER\SQLInstance': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2014-04-11 15:40:00.472 OLE DB Subscriber 'SUBSCRIBER\SQLInstance': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2014-04-11 15:40:00.478 Percent Complete: 0
2014-04-11 15:40:00.479 Applying the snapshot to the Subscriber
2014-04-11 15:40:00.480 OLE DB Distributor 'SERVER\SQLInstance': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2014-04-11 15:40:02.535 OLE DB Distributor 'SERVER\SQLInstance': select datasource, srvid from master..sysservers where upper(srvname) = upper(N'SERVER\SQLInstance')
2014-04-11 15:40:03.559 OLE DB Distributor 'SERVER\SQLInstance': {call sys.sp_MSadd_mergesubentry_indistdb (0,N'SERVER\SQLInstance',N'dbRepl',N'TEST Publication',N'SUBSCRIBER\SQLInstance',N'dbRepl',1,1,0,N'',?,90)}
2014-04-11 15:40:04.600 Connecting to OLE DB Subscriber at datasource: 'SUBSCRIBER\SQLInstance', location: '', catalog: 'dbRepl', providerstring: '' using provider 'SQLNCLI11'
2014-04-11 15:40:04.609 OLE DB Subscriber: SUBSCRIBER\SQLInstance
DBMS: Microsoft SQL Server
Version: 10.50.4000
catalog name: dbRepl
user name: rplMergeAgent
API conformance: 0
SQL conformance: 0
transaction capable: 1
read only: F
identifier quote char: "
non_nullable_columns: 0
owner usage: 15
max table name len: 128
max column name len: 128
need long data len:
max columns in table: 1000
max columns in index: 16
max char literal len: 131072
max statement len: 131072
max row size: 131072
2014-04-11 15:40:04.611 OLE DB Subscriber: SUBSCRIBER\SQLInstance
DBMS: Microsoft SQL Server
Version: 10.50.4000
catalog name: dbRepl
user name: rplMergeAgent
API conformance: 0
SQL conformance: 0
transaction capable: 1
read only: F
identifier quote char: "
non_nullable_columns: 0
owner usage: 15
max table name len: 128
max column name len: 128
need long data len:
max columns in table: 1000
max columns in index: 16
max char literal len: 131072
max statement len: 131072
max row size: 131072
2014-04-11 15:40:07.454 OLE DB Subscriber 'SUBSCRIBER\SQLInstance': sp_MSacquiresnapshotdeliverysessionlock
2014-04-11 15:40:07.526 OLE DB Subscriber 'SUBSCRIBER\SQLInstance': sp_MStrypurgingoldsnapshotdeliveryprogress
2014-04-11 15:40:07.530 OLE DB Subscriber 'SUBSCRIBER\SQLInstance': sp_MSissnapshotitemapplied @snapshot_session_token = N'\\SERVER\Snapshot\unc\SERVER$SQLInstance_DBREPL_TEST PUBLICATION\20140411082109\', @snapshot_progress_token = N'\\SERVER\Snapshot\unc\SERVER$SQLInstance_DBREPL_TEST
PUBLICATION\20140411082109\Person_2.sch'
2014-04-11 15:40:24.659 OLE DB Subscriber 'SUBSCRIBER\SQLInstance': sp_MSreleasesnapshotdeliverysessionlock
2014-04-11 15:40:24.663 The schema script 'Person_2.sch' could not be propagated to the subscriber.
2014-04-11 15:40:24.665 OLE DB Subscriber 'SUBSCRIBER\SQLInstance': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2014-04-11 15:40:24.690 Percent Complete: 18
2014-04-11 15:40:24.692 The schema script 'Person_2.sch' could not be propagated to the subscriber.
2014-04-11 15:40:24.693 OLE DB Distributor 'SERVER\SQLInstance': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2014-04-11 15:40:27.541 Percent Complete: 0
2014-04-11 15:40:27.542 Category:NULL
Source: Merge Replication Provider
Number: -2147201001
Message: The schema script 'Person_2.sch' could not be propagated to the subscriber.
2014-04-11 15:40:28.563 Percent Complete: 0
2014-04-11 15:40:28.565 Category:AGENT
Source: SUBSCRIBER\SQLInstance
Number: 0
Message: The process could not read file '\\SERVER\Snapshot\unc\SERVER$SQLInstance_DBREPL_TEST PUBLICATION\20140411082109\Person_2.sch' due to OS error 1326.
2014-04-11 15:40:28.566 Disconnecting from OLE DB Subscriber 'SUBSCRIBER\SQLInstance'
2014-04-11 15:40:28.568 Disconnecting from OLE DB Subscriber 'SUBSCRIBER\SQLInstance'
2014-04-11 15:40:28.569 Disconnecting from OLE DB Subscriber 'SUBSCRIBER\SQLInstance'
2014-04-11 15:40:28.570 Disconnecting from OLE DB Subscriber 'SUBSCRIBER\SQLInstance'
2014-04-11 15:40:28.571 Disconnecting from OLE DB Publisher 'SERVER\SQLInstance'
2014-04-11 15:40:28.573 Disconnecting from OLE DB Publisher 'SERVER\SQLInstance'
2014-04-11 15:40:28.575 Disconnecting from OLE DB Publisher 'SERVER\SQLInstance'
2014-04-11 15:40:28.577 Disconnecting from OLE DB Publisher 'SERVER\SQLInstance'
2014-04-11 15:40:28.578 Disconnecting from OLE DB Distributor 'SERVER\SQLInstance'
2014-04-11 15:40:28.579 Disconnecting from OLE DB Distributor 'SERVER\SQLInstance'
I can say it is about how can the rplMergeAgent read the Shared folder.
What do you think?

SQL Server Plugin Capabilities

Is it possible to set metrics specific for individual databases within a single instance using the SQL Server plugin? I thought maybe using user defined metrics, but I dont see that supported either. Any help is appreciated.

Are you asking about adding metrics of your own to a particular instance?
Unfortunately, UDMs are only available for Oracle DB target instances and Host instances. You could create a Host UDM for a SQL Server instance residing on the same host, but you'd have to write a script of some sort to get at the information you want.

SQL Server Plugin settings

I have been searching around and cant seem to find any information on how to define the jdbc url connection string for the SQL Server plugin with a named instance.
I have a SQL2000 server working no problem(no named instance) but I cant seem to get the SQL2005(with named instance) server working.
I have tried
jdbc:sqlserver://hostname:port\instance
jdbc:sqlserver://hostname\instance:port
jdbc:sqlserver://hostname\instance <-using default port
jdbc:sqlserver://hostname\instance:port;instance=instance
jdbc:sqlserver://hostname\instance;instancename=instance
Also should I be using the Microsoft driver or JTDS ?
I get various errors about missing properties[iscluster], its not a cluster. No matter what I think I have an issue with the url since I got the other server working.
Any help would be great
Thanks

Different Microsoft SQL Server instances communicate via different ports.
By default, the default instance communicates via default port 1433.
If your named SQL2005 instance communicates via port, for example, 1437,
the JDBC URL would be:
jdbc:sqlserver://hostname:1437
Do not enter the instance name.
To find the TCP/IP Port for a non-default SQLServer instance, access the registry editor, regedit:
HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\<Instance Name>\MSSQLServer\SuperSocketNetLib\Tcp
Use the default Microsoft driver.

What version of SQL Server support ssl connection with TLS. 1.2 (SHA-256 HASH)

Hi,
I just want to know,
What version of SQL Server support ssl connection with TLS. 1.2 (SHA-256 HASH).
if support already,
how can i setting.
plz. help me!!!

The following blog states that SQL Server "leverages the SChannel layer (the SSL/TLS layer provided
by Windows) for facilitating encryption. Furthermore, SQL Server will completely rely upon SChannel to determine the best encryption cipher suite to use." meaning that the version of SQL Server you are running has no bearing on which
encryption method is used to encrypt connections between SQL Server and clients.
http://blogs.msdn.com/b/sql_protocols/archive/2007/06/30/ssl-cipher-suites-used-with-sql-server.aspx
So the question then becomes which versions of Windows Server support TLS 1.2. The following article indicates that Windows Server 2008 R2 and beyond support TLS 1.2.
http://blogs.msdn.com/b/kaushal/archive/2011/10/02/support-for-ssl-tls-protocols-on-windows.aspx
So if you are running SQL Server on Windows Server 2008 R2 or later you should be able to enable TLS 1.2 and install a TLS 1.2 certificate. By following the instructions in the following article you should then be able to enable TLS 1.2 encryption
for connections between SQL Server and your clients:
http://support.microsoft.com/kb/316898
I hope that helps.

SQL server plugin - cluster?

Ive previously installed a sql server plugin for 11g grid control. works great.
Is there a how-to or a suppoprt note on installing for 2008 SQL server cluster? cant seem to find. In the install guide on the download link for the plugin, the versions supported are listed a
Microsoft SQL Server 2005 Cluster: Active/Active and Active/Passive

SQL Server 2008 R2 is certified on EM 11g, and will also be certified once the EM 12 version of the plug-in is released. We are working on version 2012 and should be certified soon.
Refer to MOS certify for more details.

Sql Server 2012 Encrypted Connection Accept only Internal IP

Hi Friends,
As we are using sqlserver 2012 is it possible we can configure Sql Server to Accept connection only internal ip (local) network as wel encrypted connections only , if possible please let me know how we can A chive this .
thank you.
Regards,
asad

Hello,
SQL Server TCP/IP protocol is a common protocol widely used over the Internet. It communicates across interconnected networks of computers that have diverse hardware architectures and various operating systems. Named Pipes is a protocol developed for
local area networks. In this case, you can configure SQL Server only use Named Pipes protocol via SQL Server Configuration Manager.
Choosing a Network Protocol:
http://technet.microsoft.com/en-us/library/ms187892(v=sql.105).aspx
Regards,
Elvis Long
TechNet Community Support

MS SQL Server 2005 Remote Database Connection

Hello Friends,
I have a database in SQL Server 2005, i installed SQL server with windows authentication. Now when I tries to connect to the server using Type 3 jdbc. I downloaded jdbc 1.2 driver from,
http://msdn2.microsoft.com/hi-in/data/aa937724(en-us).aspx
now i want to connect to the database from remote machine(different network).
How can i achieve this, and what setting i have to make to the sql server?
Any suggestion will be greatly appreciated.
Regards
Mohneesh

okey i done with some experiment.
now i am able to do it from local machine with the following code
String url="jdbc:sqlserver://LocalIP:1433;integratedSecurity=true;";
Class.forName("com.microsoft.sqlserver.jdbc.SQLServerDriver");
Connection conn = DriverManager.getConnection("url");
now when i move to remote system and change the Local IP to remote IP(server has static IP)
it comes up with SQLException: Login failed.for user ''.
com.microsoft.sqlserver.jdbc.SQLServerException: Login failed for user ''. The user is not associated with a trusted SQL Server connection.
please help me its kinda urgent.
Regards
Mohneesh

UD Connect to SQL Server using Remote Cube(URGENT !!!!)

Hi all,
Scenario:
I am new to Remote/Virtual Cubes and I think everyone is new to Universal Data Connect (UD Connect). I have to create a prototype using Remote Cube to create a front end reporting tool for one of our partners that does not have an SAP system. So instead of our partner buying a front end tool to do querying on their database we decided to create the solution from our BW system by using Remote Cubes with UD connect since we just upgraded to 3.5 . The legal limitation prevent us from loading the data on our system so we have to use remote cubes.
Question:
I know RCs are limited when it comes to the amount of data that they report on and the number of users that can use them but I don't have exact numbers.... I'm quiet certain that no one really know the 'exact' limit but it would help if i know the approx figures I'm working with. I need to come with with a prototype ASAP so it can be decided if we want to go ahead with this.
I would appreciate ANY help from anyone regarding this issue and if you can think of some more issues that i might encounter pls let me know. It would be great if someone who has gone thru this can guide me as well...Thank you all in advance.
ML

Hi,
1) DB Connect is something like the grandfather of UD Connect (simply put).
2) Here is some documentation about UDC:
http://help.sap.com --> SAP NetWeaver --> [release, language] --> SAP NetWeaver --> Information Integration --> SAP Business Information Warehouse --> Data Warehousing --> Data Retrieval --> Data Transfer with UD Connect
directly:
http://help.sap.com/saphelp_nw04/helpdata/en/78/ef1441a509064abee6ffd6f38278fd/frameset.htm
3) Customer Call Series recordings, presentations, etc.:
http://service.sap.com/nw-cc
(the webex session for UDConnect was on 17th March)
4) UD Connect uses the 4 Connector types that SAP provides, like XML, ODBO, JDBC and SAP Query. They same connectors are used by the Bi Java SDK, which is included in the Visual Composer by the BI Kit.
While in the UDC scenario you can either extract or remotely access the data and build structures for it, in the VC scenario you just make remote access to the data.
Performance in either case depends on the amount of data and the kind of navigation and aggregation you require on the data made on the backend system (your MS SQL Server). And of course from network, load on the systems, etc.
Servus
Mario

Unable to Access SQL Server 2005 Remotedly

Not sure if this is the right forum to post this...
After going through lot of old posts in various forums and changing lot of settings, i'm still not able to access my Server remotely.
This is Windows 2003 Server machine with Sonicwall Firewall, i have allowed Port 1433 in both Firewall and ISA and call is getting through but i'm getting following error msg :-
{"An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, 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)"}
This machine is also having Sql Server 2000, and the SQL Server 2005 is installed with named instance.
My connection string is :-
"Data Source=192.168.0.1\MYSERVER;Initial Catalog=MyDatabase;Integrated Security=True"
In example above, i'm showing dummy values but actual string is having the actual live IP address and correct named instance and database.
If i use a local address like 192.168.0.1 then i'm able to connect.
My TCP/IP Address in Sql configuration is having my Live IP Address and the port 1433.
Any help will be highly appreciable..

i'm still checking on this. i have changed the port now to 1434 and changed in all places.
my connection string is also changed now, so now i'm using :- MYIP\MYSERVER,1434
now i'm getting a different error msg
{"An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not 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.)"}
this can also be due to firewall or something else is blocking it, i will rechk n post back final answer.

MS SQL Server and JDBC Connection

I am doing on MS SQL Server 2000 with JDBC for RMI. I download driver from the Microsoft site, and used a connection statement like
con = DriverManager.getConnection("jdbc:sqlserver://localhost:1433;user=sa;password=");
unfortunately the connection didn't succeed, it says the server actively refused. connect
where is the problem? Pls anyone with solution.

BalusC wrote:
"Connection refused" roughly means that the remote server is not accessible on the specified port.
Check the correctness of the port and check if there isn't a firewall/proxy running which blocks that port.What I don't understand about the error messages, and so thought it must be related to MS SQL, rather tthan connections in general, is the phrase actively refused that he used. I take that to menat that the DB accepted a connection attempt, then, after attempting to authenticate, cut it off. But its probably just a misrepresentation of the error message on his part.
Specific MS SQL information, I don't know though.

MS Sql Server, unable to connect to server after DB table change.

I elected to move some columns from one table to another.
I ran a script to attempt to add the columns to the new table, after deleting the columns, to test the script.
After this, I was unable to do anything with the table involved, I kept getting timeout errors.
I restarted the SQL server instance.
Now, for the whole DB server ( there are multiple DB's hosted on this server ), I get messages like "cannot show requested dialog" additional information: "failed to connect to server devsql01. (Microsoft.SqlServer.ConnectionInfo)" "the
target principal name is incorrect. Cannot generate SSPI context. (Microsoft SQL Server).
How do I fix this?
Thanks in advance,
David

Hi David,
According to your description, you come across the error(the target principal name is incorrect. Cannot generate SSPI context)
Besides Uri's post, this issue could occur when there are duplicate SPNs registered in Active Directory(AD), or the SQL Server service account doesn't have the Read and Write ServicePrincipalName permissions after the change from other users.
To work around the issue, please follow the solutions below.
1.Please check if there are duplicate SPNs registered in AD using LDIFDE tool. If so, please delete them using the setspn tool. For more information about the process, please refer to the article:
http://mssqlwiki.com/2013/12/09/sql-server-connectivity-kerberos-authentication-and-sql-server-spn-service-principal-name-for-sql-server/
2.Please check if SQL Server service account has Read servicePrincipalName and Write servicePrincipalName in the Active Directory service. If it doesn't have, please grant Read and Write ServicePrincipalName permissions.
In addition, there is an article for your reference:
http://support.microsoft.com/kb/811889
Regards,
Michelle Li

Inserting data to a . SDF database (SQL Server Compact Edition connection)

Hi, all.
I'm working on a project that worked fine while connecting to SQL Server 2008. I used a connection string like this:
Driver={SQL Server Native Client 10.0};Server=myServerAddress;Database=myDataBase;Uid=myUsername;Pwd=myPassword;
Now, I've replaced all database connections in my project to work with SQL Server Compact Edition, and my connection string is something like this:
Provider=Microsoft.SQLSERVER.CE.OLEDB.3.5;Data Source=myDir\myDataBase.sdf;
After changing the type of connection, I'm getting an error on "DB Tools Insert Data.vi". This is what I get:
Error -2147217872 occurred at NI_Database_API.lvlib:Cmd Execute.vi->NI_Database_API.lvlib: DB Tools Insert Data.vi->Main.vi
Possible reason(s):ADO Error: 0x80040E30 Exception occured in Microsoft SQL Server Compact OLE DB Provider: The given type name was unrecognized. [,,,,,] in NI_Database_API.lvlib:Rec Create - Command.vi->NI_Database_API.lvlib:Cmd Execute.vi->NI_Database_API.lvlib: DB Tools Insert Data.vi->Main.vi
This is a simplified block diagram (as I said, it worked perfectly while using SQL Server 2008 connection):
Could you please help me?
Thanks in advance,
Francisco

Hi, Steve. Thanks for your answers.
I worked around this problem by using directly a SQL query instead of this function (you were right, using DBTools Execute Query VI). But now I'm getting problems with other functions, when inserting data into the DB including NULL values.
I make a SQL query like this using DBTools Execute Query VI:
INSERT INTO Table1 (Column1, Column2, Column3, Column4, Column5, Column6) VALUES ('Value1', 'Value2', 'Value3', 'NULL', 'Value5', 'Value6')
and get the following error:
ADO Error: 0x80040E07Exception occured in Microsoft SQL Server Compact OLE DB Provider: A literal value in the command could not be converted to the correct type due to a reason other than data overflow. [,,,,,] in NI_Database_API.lvlib:Conn Execute.vi->INSERT (new) restricción (DBCT).vi->Restricciones a Base de Datos (DBCT).vi->Definir - editar restricciones.vi->Main.vi
The same SQL query worked perfectly when using the SQL Server 2008 connection, so it's not a database structure issue.
Could somebody please help me?
Regards,
Francisco

Some of the SQL Server 2012 are not getting monitored in SCOM 2012 SP1.( basics monitoring is happening, expect SQL role)

Found that all the SQL servers are getting monitored, expect few servers which are having SQL server 2012 role.
proxy is enabled for these servers, when I checked discovered inventory for SQL 2012 database unable to find these servers in that list.
and other servers having SQL Server 2012 monitoring properly issue is with only few servers.

Hi,
thanks for the all the input, we are using service account as windows account instead of action account !!
will that also affect discovery of SQL role?
and also found that there are many alerts in SCOM console, with alert description :
SQL Server cannot authenticate using Kerberos because the Service Principal Name
(SPN) is missing, misplaced, or duplicated.
please let me know how we can resolve this issue, will it affect SQL discovery as well ?

SQL Server Plugin - Remote Connections to Monitor Targets

Similar Messages

Maybe you are looking for