Read Only SQL 2012 Replica DB on a SQL 2014 box

I have set up a data availability group between two SQl 2012 boxes on my windows cluster. they are failing over fine and synchronized as expected.
I want to add an additional read only replica on my SQL 2014 box which is also included in my windows cluster (so i can use this replica for reporting with 2014 In Memory features) the fail-over is still between the two 2012 boxes.
Problem is even tho i have set this replica to read only - yes, the database is always in - Synchronized / In recovery - so i can never connect to it.
Is this scenario possible?

Thanks David
Yes the whole point of this was to get access to real time data from within 2014, but the more i think about it the linked server still would not give me what i want as I belive the in memory is defined at table creation level.
With the tables being created in 2012 that would be a problem.
Thanks for the info mate.

Similar Messages

BC4J/JSP:Foreign Keys:Read Only Renderers

I've read and implemented all of the Renderers in the Renderer how to document. I've also read 8 pages of postings to this forum regarding renderers and LOVs. And I've read reams of BC4J class documentation.
Though the EditRenderer that does a lookup via a SQL query works well, there is no equivalent Read-only (via a SQL query) Renderer example.
I have tried to use the examples to create a Read-only (SQL based) Renderer but I haven't had much luck.
The closest I got to a solution was an indicator that another poster accomplishes this by modifying the generated JSP. This is clearly the wrong place to implement this functionality (doesn't allow for code re-use).
I was also able to use the DynamicEditRenderer as a Read-Only Renderer but that would confuse my users and create bugs.
It was my idea that you shouldn't have to define the SQL and that you could use existing BC4J classes to lookup the friendly FK value. I looked through the XML files for View Objects and View Links and saw all the information required to do this. A smart person (obviously much smarter than me), should be able to create a read-only and Edit Renderer that doesn't require a SQL property or the PK or column properties (use the UK from the db).
Does someone have an example of a Read-Only, SQL based, Renderer? Better, has someone written a generic renderer that can track back through View Links to find the UK in the lookup table?
This is incredibly basic functionality that I'm surprised is missing from JDeveloper.
Please help.
Thanks, George

You are not going to find an 'exact' match in our existing classes. The rednering HOWTO(http://otn.oracle.com/products/jdev/howtos/jsp/renderers.html) provides enough information for implementing your readonly lookup field. If you look at the first renderer in this document, it uses a static lookup list. You can easily use a secondary view object for your lookup values. Here is the code from that document:
package myrenderers;
import oracle.jdeveloper.html.ReadOnlyField;
import oracle.jbo.Row;
import oracle.jbo.AttributeDef;
import java.util.StringTokenizer;
public class ListFieldRenderer extends ReadOnlyField
public ListFieldRenderer()
public String renderToString(Row row)
setValueFromRow(row);
AttributeDef aDef = getAttributeDef();
String sAttrValue = getValue();
String sList = (String)aDef.getProperty("DISPLAY_LIST");
if(sAttrValue != null && sList != null)
StringTokenizer tokens = new StringTokenizer(sList, ",", false);
while(tokens.hasMoreTokens())
String sEntry = tokens.nextToken();
String sValue = sEntry.substring(sEntry.indexOf('=') + 1);
String sKey = sEntry.substring(0, sEntry.indexOf('='));
if(sKey.equals(sAttrValue))
return sValue;
return super.renderToString(row);

Database Read only

Hi All,
Can SAP application connect to read only SQL Server database ?
We are trying to use secondary database of log shipping, for our operational adhoc reporting of production data.
Please let me know.
Thanks
Mushtaq

Hi Mushtaq,
no, this is not possible. Even if you do not run any reports/transactions which you know will write to the database, the SAP system will run its internal processes and they'll write to the database. For this reason it's not possible to use a read-only DB for an SAP system.
Regards,
Beate

Read Only Thumb Drive

I'm having a problem with "permissions" for a 1G Thumb Drive. Basically, I am being offered "read only" for this thumb drive. Using Utility, I can verify the drive, but the repair permissions options is grayed out. I cannot erase and reformat either.
Using Get Info, I can see that the thumb drive is FAT16 and that the drive has "read only" permissions. I've ticked the "shared folder" box - still not able to write to the drive. There is no "ignore permissions" option offered. I have other drives of the same type that work with Leopard - just this particular one is for some reason locked into "read only".
I'm curious as to why this one, which is new and has never been used, will not work with Leopard (It works on my Panther notebook and with my Windows PC). I'm also curious as to how to change or repair permissions for this problem.
Thanks for any advice.
Jill

It may be because a Leopard Mac can't write to a FAT16 file system. Reformat to FAT32 on your Windows box and see if that fixes the problem. Repair permissions is only available for drives that contain a Mac OS, since it only repairs the components of an Apple OS install.
Francine
Francine
Schwieder

SQL 2014 performance

We have a fresh install of SQL 2014 running on Windows 2012 R2 running in Production.
We tested this extensively first and most of our code ran as fast as SQL 2012 or slightly better.
Pure engine processes such as Backup jobs run about 30% faster.
However, now that we’re in Production for the first day we’re seeing some very sporadic performance.
For example, 90% of our jobs are running just fine. 10% of the jobs are running significantly longer.
Jobs that used to take 7-8 minutes are now running in 40 minutes plus.
Not only is this slowing down our server in general but it’s causing a lot of blocking issues.
We’re convinced this is a SQL 2014 issue and not hardware.
Using iometer we can tell that this server outperforms our old server.
SQL doesn’t always substantiate the numbers we’re seeing from iometer as far as performance compared to our old server.
We’re running on RTM, not Cumulative Update 1.
Our hardware is a beast of a server; DL580 G8, 384 GB ram, only 2 physical hard drives (running the OS/SQL) and the rest are Fusion iO cards.
We have 9 total Fusion cards for the database, log and tempdb.
Our old server is also a very robust server: DL380 G8, 384 GB ram, 48 physical drives and 2 Fusion iO cards for tempdb.
Has anyone else deployed SQL 2014? Has anyone else encountered these sporadic performance issues?
If so, did cumulative update 1 fix the issues?
Separate question: If I put my database in 2012 compatibility mode and do a backup, can SQL 2012 read the SQL 2014 backup?
Thanks in advance,
André
André

We applied CU2 last night. Things seem to be better this morning but we're still seeing some differences between SQL 2012. Here are 2 of the biggest issues we're seeing.
1 - views are slow. We have queries that use views that are taking forever. In some cases the view might be a simple "select 10 fields from table" type of views. If we change our query to use the base table instead of the view, the query
finishes very quickly. As an example, a query using the view takes 3 minutes. If we change the query to use the base table instead of the view it finishes in 5 seconds.
2 - inner joins are slow compared to "not exists" or "exists". Back when we migrated from SQL 2000 to 2008 we were told that joins were faster, so we migrated our code to use joins and our code flew. Now we're seeing performance issues on some,
but not all, queries that use joins.
3 - inner joins are not able to see the outside table. For example, this query worked just fine in SQL 2012, and it throws an error in 2014
select
top100
fromcustomers c(nolock)
inner
join(selectcorpnumber,fdate,code
fromdbo.FN_Customers_ParseCodes(c.rcode,c.corpnumber,c.fdate))r
onr.corpnumber=c.corpnumber
where
c.importtimestamp='2014-06-30
15:37:17.347'
and
c.customerid='123'
The error it throws is:
Msg 4104
,Level16,State1,Line
2
The multi
-part identifier "c.codes" could
notbe bound.
Msg 4104
,Level16,State1,Line
2
The multi
-part identifier "c.corpnumber" could
notbe bound.
Msg 4104
,Level16,State1,Line
2
The multi
-part identifier "c.fdate" could
notbe bound.
André

SQL Server 2012 - Wat Is The Best Solution For Creating a Read Only Replicated/AlwaysOn Database

Hi there I was wondering if someone may have a best recommendation for the following requirement I have with regards setting up a third database server for reporting?
Current Setup
SQL Server 2012 Enterprise setup at two sites (Site A & Site B).
Configured to use AlwaysOn Availability groups for HA and DR.
Installed on Windows 2012 Servers.
This is all working and failover works fine and no issues. So…
Requirement
A third server needs to be added for the purpose of reporting, to be located on another site (Site C) possibly in another domain. This server needs to have a replicated read only copy of the live database from site A or Site B, whichever is in use. The Site
C reporting database should be as up-to-date to the Site A or Site B database as possible – preferably within a few seconds anyway….
Solution - What I believe are available to me
I believe I can use AlwaysOn and create a ReadOnly replica for the Site C. If so do I assume Site C needs to have the Enterprise version of SQL server i.e. to match Site A & Site B?
Using log shipping which if I am correct means the Site C does not need to be an Enterprise version.
Any help on the best solution for this would be greatly appreciated.
Thanks, Steve

for always on - all nodes should be part of one windows cluster..if there site C is on different domain - I do not think it works.
Logshipping works --as long as the sql on site C is is same or higher version(sql 2012 or above). you can only do read only.
IMHo, if you can make site C in the same domain then, Always is better solution else log shipping
also, if your database has enterprise level features such as - partitonin, data compression -- you cannot restore the database on lower editions- so you need to have enterprise edition.
Hope it Helps!!

Linked Server from SQL 2008 to Connect to 2012 read only replica never works

I have two Production Database Servers
1. SQLServer2008 (2 Nodes Cluster)
2. SQLServer2012 with 2 read only replica (3 Nodes Cluster)
I would like to draw a line here, We have routing table and URL working perfectly fine.
We have tested LINKED Server from 2012 Box to production Server by Specifying APPLICATIONINTENT = ReadOnly; it works perfectly fine, the routing is being used.
When we create linked server from SQL Server 2008 Box (Please note we have installed SQL Server 2012 Client tools on this box and Restarted the Servers) using the below script
USE [master]
EXEC master.dbo.sp_dropserver @server=N'AGL1', @droplogins='droplogins'
GO
EXEC master.dbo.sp_addlinkedserver @server = N'AGL1'
,@datasrc='AGL1'
,@provider='SQLNCLI11'
,@provstr='ApplicationIntent=ReadOnly;Database=AdventureWorks2012'
Linked Server is created, Now when I run the Query
exec ('select @@servername') at AGL1
It always brings the Primary READ/WRITE node name only, after lots of research I found that, this linked Server is always using SQL Native Client 10.0 only, even after creating Linked Server using SNC 11, That is the reason it is not going to routing
table. Its always connecting to Primary node.
Below is the way I found it, on 2012 Production Server I executed below Query
SELECT session_id, protocol_type, driver_version =
CASE SUBSTRING(CAST(protocol_version AS BINARY(4)), 1,1)
WHEN 0x70 THEN 'SQL Server 7.0'
WHEN 0x71 THEN 'SQL Server 2000'
WHEN 0x72 THEN 'SQL Server 2005'
WHEN 0x73 THEN 'SQL Server 2008'
ELSE 'SQL Server 2012'
END,client_net_address ,client_tcp_port,local_tcp_port ,T.text
FROM sys.dm_exec_connections
CROSS APPLY sys.dm_exec_sql_text(most_recent_sql_handle) AS T
The help is taken from msdn (Link Provided below) for the above Query
https://msdn.microsoft.com/en-us/library/dd339982.aspx
and I found it always uses SQL Server 2008 SNC.
My Question is, is there a way to force SQL Server to use SQL Server Native Client 11.
Has anyone tried this setup?
Thank you in advance.

Unfortunately no, there is no other way of forcing it without restart. The SQL Server stack has no idea of the existing Native Client as it booted prior its installation. And you cannot force "DLL reload" without proper service restart.
Ivan Donev MCT and MCSE Data Platform

SQL 2012 AlwaysOn cluster IP not moving after failover, causing database to be read-only

SQL Server Cluster Name: SQLDAG01
SQL Server Cluster IP: 10.0.0.50
Cluster Listener IP: 10.0.0.60
Node 1 Name: SQL01
Node 1 IP: 10.0.0.51
Node 2 Name: SQL02
Node 2 IP: 10.0.0.52
Everything is fine when SQL01 is the primary. When failing over to SQL02, everything looks fine in the dashboard but for some reason the cluster IP, 10.0.0.50, is stuck on node 1. The databases are configured to provide secondary read access. When executing
a query on SQLDAG01, I get an error that the database is in read-only mode. Connectivity tests verify that SQLDAG01, 10.0.0.50, connects to SQL01 even though SQL02 is now the primary.
I've been Googling this for the better part of the day with no luck. Any suggestions? Is there a Powershell command force the cluster IP to move to the active node or something? Also I'm performing the failover as recommended, from Management Studio connected
to the secondary node.

This was the answer, it had been setup to use the cluster name instead of the application name. Whoever installed Sharepoint connected it to SBTSQLDAG01 instead of SHAREPOINT01. Once we changed Sharepoint to connect to SHAREPOINT01, the failover worked as
expected. We did have a secondary issue with the ARP cache and had to install the hotfix from http://support.microsoft.com/kb/2582281 to resolve it. One of the Sharepoint app servers was failing to
ping the SQL node after a failover, the ARP entry was stuck pointing to the previous node. This article actually helped a lot resolving that: http://blog.serverfault.com/2011/05/11/windows-2008-and-broken-arp/
One thing I did notice is that the SQL failover wizard does not move cluster groups "Available Storage" and "Cluster Group", I had to move those through the command line after using the wizard. I'm going to provide the client with a Powershell script that
moves all cluster groups when they need to do a manual failover. This also happens to be why the Sharepoint issue started, "Cluster Group" is what responds to the cluster name SBTSQLDAG01. Moving that group over to the node that has the active SQL cluster
group also made it work properly, but using the application name is the correct method.
Thanks everyone for all your help. Although the nitpicking about terminology really didn't help, that was a pointless argument and we really could have done without it. Yeah I know 2008 called is "Failover Cluster Manager" and MSCS is the "2003 term" but
really, they're basically the same thing and we don't really need to derail the conversation because of it. Also, If you look at the screenshot below you can clearly see "AlwaysOn High Availability" in SQL Management Studio. That's what it's called in SQL,
that's where you do all the work. Trying to tell me it's "not a feature" is wrong, pointless, and asinine, and doesn't get us anywhere.
Sorry it took so long to get back, I was off the project for a couple weeks while they were resolving some SAN issues that caused the failover to happen in the first place.

Backup Maintenance Plan on SQL AlwaysOn Availability Group Secondary Read-Only node

I have 3 node SQL 2012 AlwaysOn Availability nodes with the 3rd node as Read-Only.
The backup job within SQL Maintenance plan is failing with the following error:
Failed:(-1073548784) Executing the query "declare @backupSetId as int
select @backupSetId =..." failed with the following error: "Cannot open backup device 'C:\\SQLDBName_backup_2014_06_08_170156_9292095.bak'. Operating system error 2(The system cannot find the file specified.).
VERIFY DATABASE is terminating abnormally.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
I have verified the SQL AlwaysOn Backup preference to be "Prefer Secondary"
Is there any special steps/settings I need to do to setup and run the backups using maintenance plan in SQL AlwaysOn?

Hi,
I'm marking the reply as answer as there has been no update for a couple of days.
If you come back to find it doesn't work for you, please reply to us and unmark the answer.
Thanks.
Tracy Cai
TechNet Community Support

SQL Server 2005 replaced with SQL Server 2014 trying to connect front end Access as guest (read only ODBC)

We have replaced a SQL Server 2005 with a SQL Server 2014 (new physical server.) Have the new server set up to use SQL Server login OR Windows user login. Had old server connecting (for a particular DB) to front end Access (2010 or 2013) as guest for
anyone logged into the Windows NT Network with a read only ODBC connection. Have the DB in the new server set to include guest as db_datareader (with only SELECT permission for the securables of each table and view being linked) but when any Windows user not
specifically listed as a SQL DB user tries to use the front end they get an error of:
Microsoft SQL Server Login
Connection failed:
SQL State: '28000'
SQL Server Error: 18456
[Microsoft][OCBC SQL Server Driver][SQL Server] Login failed for user {domain\user}.
After closing that pop-up window a server login window appears. Of course, since the guest user is not specifically listed as a user in the DB that fails also. It seems like there should be a very simple solution to this, but I can't seem to find it. I want
to allow anyone logged in on the Windows system (locally) to be able to open the MS Access file (on their work station machine) and run their own (read only; select) queries on the SQL Server database. Any suggestions?
Thanks a billion in advance ----

Thanks for the response Olaf. I have now spent weeks researching this. I realize that using the guest account in most situations is not advised. As mentioned, I have restricted the guest account to allow the db_datareader role only, and have explicitly denied
all other roles, as well as allowing select only, and still have no access for the guest account.
The suggested fix in the second link you provided, of using Windows groups is not plausible for my situation either. We are a scientific field research institution, with a few long term users and lots of users that may have Windows accounts for a few months,
and then they are gone. It would be a nightmare for the network tech to try to keep a group account up to date, and we need to give access (read only, of course) to anyone logged into the system. Realize that the ONLY access of any kind to this database is
thru MS Access ACCDB, using a (by default) read only OCDB connection.
This type of access is used particularly because researchers need to be able to set up their own queries, and the MS Access query interface is particularly convenient for people who are not themselves SQL experts, yet are trying to get some very advanced
levels of output. Putting the database online is not practical because then we are back to the need for a comprehensive query interface, and just picking up general subsets of the data online (from a basic web page search feature) would be out of the question,
since the result set would involve hundreds of thousands if not millions of records.
So - that said - what exactly would you suggest, assuming we don't have the funds to buy a whole new system, and have spent plenty of money with Microsoft's Enterprise level MS Office so that all work stations have MS Access, and Microsoft's SQL Server,
as well as running our network on Microsoft's network software.

Remove Standby/Read only mode for a database in sql server 2005

Hi,
I have a problem in sql sever . my database is showing standby/read-only mode. i want to remove that mode.please help me for the issue.

HI
Did you assign any DB read only user?
check the administrator guide in your SAP Business one->Documntation->system setup->Administrator guide...
but removing DB read only user is impossible.....

SQL Developer in Read-Only-Mode

Oracle SQL Developer version 1.2.1 BUILD MAIN-32.13
Running under WinXP
Issue description:
Impossible to start SQL Developer in Read-Only-Mode for certain users who should not be able to modify any data.

The feature is under consideration in http://htmldb.oracle.com/pls/otn/f?p=42626:39:3043613241465472::NO::P39_ID:4701, but something similar was previously rejected in http://htmldb.oracle.com/pls/otn/f?p=42626:39:3043613241465472::NO::P39_ID:2741 ...
K.

I want to give a user to read only rights on sql server agent 2008

I want to give a user to read only rights on sql server agent 2008.When I giving SQLAgentuser Role then user is only able to view SQL Server agent as Green but no job visible in job activity monitor.Currently he has db_reader rights on one user database.
What rights should I give?
Thanks

There are 3 SQL server Agent fixed database roles in sql server.
1.SQL AgentUSerRole:- To create and manage jobs
2.SQLAgentReaderRole: To grant read acces.
3.SQLAgentOperatorRole : to run and delete jobs.
For you question you can create a user and grant him SQLAgentReaderRole.
Example:
Create LOGIN test with Password='abc'
Use msdb;
GO
Create User test for login test
use msdb;
EXECUTE sp_addrolemember @rolename='SQLAgentReaderRole',@membername='test'
Hope this solves your problem!!!

DSplugin psw on read-only replica

I am running a Directory Server 6.3 which is a master to 2 read-only consumers (one is DS 6.3, one is DS 5.2). Replication is working to both consumers.
On the master server, I have ISW for Windows 6.0.
I am able to sync passwords from AD to the master DS. That is working fine. When a user changes their password in AD; then authenticates against the master DS server, the new password is pulled from AD.
I am having trouble when a password is changed on AD and the user tries to authenticate to the read-only replia. They get an Authentication error. I think I have the DS plugin installed on both of my read-only servers. I can not figure out why they won't send the request to the master server to get the password from AD. pswvalidate does get set to True.
My master server has 2 interfaces (master-if1 and master-if2) and the 6.3 readonly replica can only reach master-if2.
# ./idsync printstat -D "cn=Directory Manager" -w secret -s dc=mycompany,dc=org -q anothersecret
Exploring status of connectors, please wait...
Connector ID: CNN100
Type: Sun Java(TM) System Directory
Manages: dc=mycompany,dc=org (ldap://master-if1.mycompany.org:389) (ldap://master-if2.mycompany.org:389)
State: SYNCING
Installed on: master-if.mycompany.org
Plugin SUBC100 is installed on ldap://master-if1.mycompany.org:389
Plugin SUBC101 is installed on ldap://consumer6.3.mycompany.org:389
Connector ID: CNN101
Type: Active Directory
Manages: mcnc.org (ldap://ad1.mycompany.org:389) (ldap://ad2.mycompany.org:389)
State: SYNCING
Installed on: master.mycompany.org
Sun Java(TM) System Message Queue Status: Started
Checking the System Manager status over the Sun Java(TM) System Message Queue.
System Manager Status: Started
SUCCESS
I see no errors in any log files I can find. I can provide more information if needed.
Thanks, Carole

Is there any experience in an environment with a master DS (6.3) server, read-only consumer servers and Identity Synchronization for Windows?
I am not able to get authentication queries to my ro consumers to poll the master DS which in turns pulls the new password from AD.
Thanks, Carole

Making sql server database read -write from read only

hey guys
i attached adventure works in sql server 2008 and it showing as read only ,
so please guide me to make it read write or remove read only tag from database
thanks in advance
sujeet software devloper kolkata

Hi,
Is there an error message while you attach (Or restore) the database if so please provide it.
If no Right click on your database choose properties -> go to options -> scroll to end then change read only option to false
I hope this is helpful.
Elmozamil Elamir
MyBlog
Please Mark it as Answered if it answered your question
OR mark it as Helpful if it help you to solve your problem
Elmozamil Elamir Hamid
http://elmozamil.blogspot.com

Read Only SQL 2012 Replica DB on a SQL 2014 box

Similar Messages

Maybe you are looking for