Replication from SQL Server Express Database to SQL Server Standard Database - sql-server

Is it possible to set up a replication between an SQL Server Express Database that we can't touch, with an SQL Server Standard database?
We only have read-only access on the SQL Server Express database, so we are oblige to use only SQL requests.
We thought of using a python script and doing the replication ourselves, but is there a framework that can do that ?
We don't need realtime replication, a time span of minutes is enough.

Related

SQL Standard Server Transaction Log for an SQL Express Server

I have an SQL express Server whereby the Transaction log becomes full.
Given the Edition of SQL server it cannot be directly managed with various tools like in the Standard Edition of SQL Server.
We do have another SQL Server - Full Standard version used in this environment as part of a larger system.
To anticipate the question: No we cannot add this database to that server.
Is there any way we can utilize the power of Standard SQL server to handle the Transaction logs for the SQL express server?
As if the Transaction Log was being handled by our full SQL Server with the tools available there?

SQL Server agent backup SSAS database

I want to use the SQl Server agent to backup one of my Analysis servers databases.
However, when I connect to my Analysis Services I have to access to the SQL server agent.
It only shows up when I connect to my Database Engine. So now when I try to schedule a backup it says it cannot find the Database. How am I supposed to do this?
Is the SQL server agent supposed to show up when connecting to my Analysis Services?
SQL Server Agent needs access to the relational database engine, as it saves its configuration and the job execution details which you can see as the job history in tables of a relational database. Actually, it uses the msdb database which is part of every SQL Server relational database instance. Thus, you need to access the relational database engine in order to access SQL Server Agent. But there is no requirement that the machine running SQL Server Agent is the same as the one running Analysis Services. Both can run on different machines, and even have different versions of SQL Server.

Is there any way to connect Oracle DBLink with SQL Server AAG Read Intent (Read Only)

There are two database server, the first using oracle database and the second using SQL Server database.
We are created Database Link (DBLink) from oracle to SQL Server to read the data for reporting purpose, and the SQL Server using replication to replicate data from Principal database.
Now we have planning to using AAG for HA, and planning to change replication into Read Only database (AAG Feature).
Is there possible using DBLink to connect to AAG SQL Server Database using Read Intent ?

Transactional Replication - Can it be used on a shared server?

Transactional Replication - Can it be used on a shared web server with MS SQL 2005 Express ?
Yes, it can but SQL Server express can only be a transactional subscriber. You will not be able to publish from it, but can publish to it.
Note that there will be some contention between SQL Server Express and a web server, so such a deployment is not scalable in the long run.

SQL Server 2005 and 2008 in conjunction

Is it recommended to use two versions of SQL Server (2005 and 2008) for storing data of an application. We have a situation where we have an existing web application consuming SQL server 2005 as a database. Some enhancements in the application required us to solution a FILESTREAM data store. Now we have our data in SQL Server 2005 and associated FILESTREAM data in SQL Server 2008. Being very new to SQL Server I would like to ascertain how bad is this in terms of performance? How can we achieve atomicity across both the database versions, is it via using a linked server or some other mechanism? Any alternative solutions would be fine except that we just cannot migrate the existing application to SQL Server 2008.
To keep your transactions ACID, you can use distributed transactions at a stored procedure level, or from a code level using DTC (e.g. via a .net TransactionScope). DTC would need to be present on both SQL Servers, and on your App Server as well if you do the ACID from there. There is some overhead with DTC
Edit : You will also need to link the servers with sp_addlinkedserver and provide credentials with sp_addlinkedsrvlogin

Resources