Lync Monitoring Database, Named Instance, Always On

I have a SQL Server 2012 named instance (LYNC_MONITOR) on a specified port which is Always On enabled for deploying LYNC 2012 Monitoring and Reporting. I had moved the databases from another DB server into a Always On AG, which works fine, and set
up Listener on the defined port. My issue comes in when changing the topology. In the topology builder, the requested information is server name and instance (default or named). Well an AG Listener on a specified port is neither of those. If the instance was
actually default, then it would be no problem (but the default instance is SharePoint). So I need to be able to provide the Listener/port combo as the server name without specifying the instance. Currently it's just pointed to the primary node (server/instance).
Does anybody know of a way to get around this? Thanks much.
Tim Hacker

Currently SQL Always On is not supported for Lync 2013. That being said have you looked at setting up a SQL Alias (cliconfg.exe) on the Front Ends? I've used this when the SQL port is not the standard one: http://blogs.technet.com/b/nexthop/archive/2011/04/12/using-lync-server-2010-with-a-custom-sql-server-network-configuration.aspx
Please mark posts as answers/helpful if it answers your question.
Blog
Lync Validator - Used to assist in the validation and documentation of Lync Server 2013.

Similar Messages

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 ..

Always on listener on named instance. Do I have to specify the port while connecting a listener created on a named instance?

Hi all. Here again.
Scenario: I have to consolidate several physical servers with one SQL server instance install on each one. I decided to consolidate all in one server installing different named instances. In order to avoid application connection string change I had the idea
of configuring different listener pointing to different alwayson group.
To meet this requests, I configured the cluster, I installed a principal SQLServer Instance and configured the alwayson groups with the required listeners.
All ok so far, alwayson is great.
So, I installed a named instance, I configured the necessary alwayson groups and the related listener but...
NOTE: The db in the principal and in the named instance have the same name.
If I connect the listener pointing the ag belonging the named instance I connect to the principal instance!
the only way I have to connect to the named instance is to specify the port that must be different from the 1433 as usual.
Anyway, why I cannot use the 1433 port if dealing with a different ip?
Listener are the following:
Named instance
10.100.21.100 : 1455
Principal instance
10.100.21.50 :
1433
Thankyou

Hi all.
I reviewed the architecture installing only named instances and I solved.
Anyway, i'm going to explain better my configuration in order to understand where I went wrong.
I have two servers, SQLCLU01 and SQLCLU02 partecipating to AVSQLCLU cluster
Each server has two SQL instances, the principal SQLPROD and the named instance SQLTEST
Each instance contain the OneToOne database.
I created an AG named AgOneToOneProd laying on the SQLPROD instance with its
OneToOne listener described here down (sys.dm_tcp_listener_states;)
7 10.100.21.50
1 1433
0 TSQL
0 ONLINE
2014-05-07 10:23:04.113
DnsName:OneToOne
Port:1433
IpconfigurationFromCluster:('IP Address: 10.100.21.50')
So I tried to create an AG named AgOneToOneTest laying on the SQLTEST named instance with its
OneToOneTest listener but the port 1433 is unavailable even if the listener IP is different. I managed in creating the listener changing the port like this
7 10.100.21.100
1 1455
0 TSQL
0 ONLINE
2014-05-07 10:36:05.347
DnsName:OneToOneTest
Port:1455
IpconfigurationFromCluster:('IP Address: 10.100.21.100')
So, the issue is:
Connecting to OneToOne.mydomain.local i can see the OneToOne database and crud operation are performed against the SQLPROD instance.
But connecting to OneToOneTest.mydomain.local the OneToOne database I'm connected to is still the one belonging to the
SQLPROD instance.
The only way to let my application connected to the SQLTEST instance is to specify the port in the DSN.
Anyway, summary here, issues are bolded
OneToOne.mydomain.local -------> SQLPROD
OneToOneTest.mydomain.local -------> SQLPROD
OneToOneTest.mydomain.local,1455 -------> SQLTEST
The same by IP
10.100.21.100,1455 --------> SQLTEST
10.100.21.100 --------> SQLPROD
and.....
10.100.21.100,1433 --------> SQLPROD
May be... Do I missed some best practices in creating listeners against a principal + named instances?
Thankyou
Stefano
Ste'

ADMIRAL database on SQL 2008 R2 Named Instance

Hi,
we are running TES 6.1.0.133 (test Master) upon a remote SQL 2005 SP4 named instance database, all is right.
I need to move the ADMIRAL database to an SQL 2008 R2 SP1 named instance.
What JDBC, JRE and connection string do I need to succeed ?
The versions are JRE 1.6.0.30, Microsoft JDBC 4.0.
thank in advance you for your experience,
Frederic

You should probably ask Cisco to help you through this they can likely provide you with an updated document and jar file
You will need to update your master.props settings.
You will need potentially need a new jar
Perform on a maintenance weekend with a maximum amount of recovery time
I have a Cisco doc and Zip files from 2010 when we did this but it is likely a different JAR that you would want to apply now.
What I would think are the Sequence of events (disclaimer Cisco would be best source of sequence, order, etc)
set system queue to zero
close all client sessions
stop master services
kill all connections to Admiral database
backup admiral database
set database offline and rename
Restore admiral database backup to new target SQL server 2008 instances
Creare a backup of master.props
Apply Jar to update master / SQL scripts (if supplied by Cisco)
Update master.props with new settings
JdbcURL=jdbc:sqlserver://:;selectMethod=cursor;databaseName=Admiral (or Admiral DB name)
There could be other setting that may also need to chance
Start Tidal Master make sure it is running
Connect Client
Verify Connections
Turn on System Queue slowly ramp up from a few to your standard level

Move Lync 2010 database in different drive in same sql instance

Hi,
I am using Lync 2010 enterprise version and Lync database in SQL cluster.
I have to move lync 2010 database files in different drive due to some space issue in the drive.
Thanks

Hi Deepak Srivastava,
As far as I know, I recommend that you move databases by using the ALTER DATABASE planned relocation procedure .
In simple terms, the steps are following:
1. Backup the Database.
2. Stop the services on Lync Servers.
3. Move the database, and you could refer to this article:
Move System Databases
http://msdn.microsoft.com/en-us/library/ms345408.aspx
4. Start the services on Lync Servers.
5. Test the Lync feature.
Hope it can be helpful.
Best regards,
Eric

Can we use sql default data base for deploying lync monitoring

Hi,
I just want to know whether i can install monitoring server using lync server default instance of sql server.
because i got an error stating "Cannot access LcsCDR or QoEMetrics on Monitoring back-end database. Verify that these databases have been deployed, and that access to the Monitoring back-end database is not blocked by the firewall".
But when i use the named instance then it is working fine. can any body tell me why it is happening.
Regards,
Aslam

Hi,
You can use default instance as describe in the following link:
http://blogs.technet.com/b/nexthop/archive/2011/06/27/deployment-details-for-lync-monitoring-reports.aspx
Please refer to Installation section.
Please make sure the account you used to deploy Monitoring Server reporting service has the required permission of your Monitoring Database.
In addition, please double check the following limits of databases for Lync Server:
You can collocate each of the following databases on the same database server:
Back-end database
Monitoring database
Archiving database
You can collocate any or any or all of these databases in a single SQL instance or use a separate SQL instances for each, with the following limitations:
Each SQL instance can contain only a single back-end database, single Monitoring database, and single Archiving database.
The database server cannot support more than one Front End pool, one Archiving Server, and one monitoring Server, but it can support one of each, regardless of whether the databases use the same SQL instance or separate SQL instances.
Kent Huang
TechNet Community Support

DBACOCKPIT - MSSQL Named Instance, RFC and DB Connection different systems

Hello All,
SAP is installed as a Central Server. Database and Central instance on a single host with the database on a Named Instance.
I have configured the dbacockpit as per SAP Note 1388700 - SQL Server Remote Database Monitor in Solution Manager 400 for my Named Instances. I have a working database connection %_<SID>_<HOSTNAME> with the DBCO Connection Info referencing the MSSQL_SERVER as <HOSTNAME>\<SID>. Full line:
MSSQL_DBNAME=<SID> MSSQL_SERVER=<HOSTNAME>\<SID> OBJECT_SOURCE=SAPSolMan710
In dbacockpit now as an additional action I try to edit the connection. I select the checkbox by RFC destination, first message with a Red LED is 'This is not the local system, please specify a RFC destination. I select any RFC destination referencing the host, even custom made ones. The response after logging in to the target (when not using Trusted RFC) is always the same.
'Red LED', SMP, RFC destination and database connection describe different systems.
In the home screen of dbacockpit if you now select 'SLD System Import' the systems with a Named Instance are still available under 'New Database Systems in the SLD'.
Now edit the system again, remove the RFC destination and Save. This will write to the SLD.
If you now log in to the SLD, Administration, Content Maintenance, 'Class' Database Systems you will now have a new System with 0(zero) associations. This system has SystemHome = <HOSTNAME>\<SID> as such it will not match to the SAP System. I have edited the Database in SMSY to directly reference the Database connection but even this does not help
Has anyone come accross this? What is the resolution?

Hi,
Could you please post the errors that appears while configuring in the DBACOCKPIT t code at the bottom of the screen?
According to that we can determine, whether it is able connect the database correctly or not.
Cheers

Co-location of persistent chat and monitoring databases on Standard Edition server

Hello, I've seen all kinds of different answers to this question around the web with conflicting answers.
We have a basic IM/Presence only install of Lync 2013 and now want to deploy Monitoring and Persistent Chat roles.
As per this blog, it states you can co-locate all of these on one FE server.
http://windowspbx.blogspot.ca/2012/07/aaa-donotpost-install-lync-standard.html
Which does match what this TechNet article states:
http://technet.microsoft.com/en-us/library/gg398131.aspx
However, in the Blog, it says you need to install Full SQL Server 2008 in order to collocate, yet this goes against what TechNet says is possible, in that you can have all databases in one instance:
Each SQL instance can contain only a single back-end database (for an Enterprise Edition Front End pool), single Monitoring database, single Archiving database, single persistent chat database, and single persistent chat compliance database.
I guess my question is, can I simply install Monitoring and Persistent Chat using the same default SQL Server 2012 instance that was installed along with the Front End Standard Edition server (RTC instance)? Or should I create a new instance? Or do I need
to install a new SQL Server 2012 somewhere on a different server altogether?
Thanks!

Hi,
Lync standard edition server has SQL express database by default to host RTC instance. Monitoring server required SQL reporting services, SQL express does not have reporting components part of it. Hence, you required full SQL version for monitoring
and archiving deployment.
Technically, you can install full SQL server on the standard edition server itself. But , it is not recommended in production environment. It's good idea to install SQL server on a dedicated server for hosting monitoring and archiving database.
Thanks
Saleesh
If answer is helpful, please hit the green arrow on the left, or mark as answer. Blog : http://blogs.technet.com/b/saleesh_nv/

Lync backend databases and Lync local databases placement best practices

We are deploying Lync 2013 for 30,000 Lync users across 2 pools in 2 datacenters. Dedicated SQL server for Lync to host all databases for FE, PC and monitoring roles.
Can anyone provide guidance around disk drives for SQL databases and local databases?
Lync backend databases
Planning for Lync Server 2013 requires critical thinking about the performance impact that the system will have on your current infrastructure. A
point of potential contention in larger enterprise deployments is the performance of SQL Server and placement of database and log files to ensure that the performance of Lync Server 2013 is optimal, manageable, and does not adversely affect other database
operations.
http://blogs.technet.com/b/nexthop/archive/2012/11/20/using-the-databasepathmap-parameter-to-deploy-lync-server-2013-databases.aspx
Is it recommended to place all Lync DBs on one drive and logs on one drive or separate onto multiple drives using Databasemappath?
Lync 2013 local databases
In the Capacity Planning Guidance Microsoft
describes that the disk requirements for a Lync 2013 front end server, given our usage model, is eight disks configured as two drives.
One drive will use two disks in RAID 1 to store the Windows operating system and the Lync 2013 and SQL Express binaries
One drive will use six disks in RAID1+0 to store databases and transaction logs from the two SQL Express instances (RTCLOCAL and LYSS)
Is this enough or should we separate the local DBs and logs onto separate drives as well? Also how big do the local DBs get?

During the planning and deployment of Microsoft SQL Server 2012 or Microsoft SQL Server 2008 R2 SP1 for your Lync Server 2013 Front End pool, an important consideration is the placement of data and log files onto physical hard disks for performance.
The recommended disk configuration is to implement a 1+0 RAID set using 6 spindles. Placing all database and log files that are used by the Front End pool and associated server roles and services (that is, Archiving and Monitoring Server, Lync Server Response
Group service, Lync Server Call Park service) onto the RAID drive set using the Lync Server Deployment Wizard will result in a configuration that has been tested for good performance. The database files and what they are responsible for is detailed in the
following table.
http://technet.microsoft.com/en-us/library/gg398479.aspx
Microsoft's technet recommendation contradicts the blog recommendation for Lync 2010.

Lync Monitoring - Media Quality Diagnostics Reports are empty?

Hi all
We have a working Lync Monitoring solution, which I've used for various troubleshooting. However now for the first time I wanted to view some media quality data and there doesn't seem to be any? I can view the user activity reports and everything just fine,
but any report related to QoE seems to have no data. We have enabled purging and gathering of QoE data and the retention period is 60 days.
I don't know where to go from here. Any ideas? I was thinking about looking in the sql database to see if there is any data, but unfortunately I'm unsure which database to check and what query command i should use on which table.
Thanks for any help you can provide.

Hello Casper
my first point of reference would be to take a look into the QOE database to see if there is any information of interest in their.
Also it might be work checking that the backend services are running for the instance to which the QOE database is associated with.
Regards
Iain Smith 
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer". Thanks Again!
http://www.northernlync.co.uk or twitter @northernlync

Database vs instance

Can anyone tell me the difference between a database and an instance?
I have heard the terms being used interchangably without knowing the actual meaning of the two.
Thanks.

It's a really messy situation, the way people make use of it. The context of the discussion is usually the only way to know what someone is actually referring to.
I've seen an Oracle instance defined as a set of certain processes running on a system. I think this includes such things as the database writer (DBWR), log writer (LGWR), and recovery processes (SMON and PMON). The OCP exam preparation book for the DBA exams has this definition in detail.
I've always considered a database to be a collection of tables that make up a specific system or serve a particular purpose, but the Oracle definition refers to a database as certain files that it controls.
The two terms are frequently used as though they are synonymous. When an instance is started, the background processes I mentioned above start running on the sytem. Then, when a database is opened, the control files associated with a particular database are opened and the datafiles associated with it are verified.
At the time a database is created with the CREATE DATABASE statement, certain datafiles and control files are defined and created. Then these files always make up the database that you've defined.
As an example, I could have a hardware system named SUPERCPU. When I start the instance named SUPERDB, some processes start running on SUPERCPU. There are a few files associated with this instance, which we generally don't deal with, except for the intialization parameters. Then when I open a database named PAYROLL, the files that were created with the CREATE DATABASE PAYROLL statement are opened and accessed by the processes running for the instance SUPERDB.
On most hardware platforms it is possible to have multiple instances running simultaneously. Each instance gets its own set of processes. It is possible to issue multiple CREATE DATABASE statements for a single instance, so you could have multiple databases running on a single instance. Most frequently, though I've seen just one database associated with one instance; if there's a need for another database, people will start another instance. Then, finally, of course, you could create a set of tables for your payroll application and call that your payroll database. You could also create a set of tables for your accounts receivable application and call that your AR database. These two sets of tables could reside in the same Oracle database.
The only way I've been able to keep these things straight as I move from installation to installation is to take them in context. Using the above example, if someone refers to SUPERDB, then they probably mean the instance running on SUPERCPU. If someone refers to the payroll database, they probably mean either a specific Oracle database or certain tables within some Oracle database.
As you can see, this whole issue is confusing. Take a look at some of the Oracle DBA books for the real definitions, then apply what you know to the context of the discussion.
null

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

Lync Monitoring Database, Named Instance, Always On

Similar Messages

Maybe you are looking for