Getting this warning when trying to setup a transactional replication. This error occurs when setting up a subscription from sql server express using non impersonated login to the distributor. this works using sql server developer subscrption to sql server workgroup publication but not from sql express to sql workgroup. Im not sure if it is an issue with the agent or what not but the subscription setup is identical to my working subscription other than the ability to choose the login to the sql server agent.
If I'm reading this correctly, you're trying to use SQL Server Express as your publisher. SQL Server Express can only be a subscriber in a transactional replication.
http://www.microsoft.com/sqlserver/2005/en/us/compare-features.aspx#integration
Related
I'm trying to access data on a SQL Server with Azure Data Studio. When connecting to the server it shows a SQL Database and a SQL Pool under Databases. I can see and interact with the Tables of the SQL Database but not with the SQL Pool.
When I use the same connection in SQL Server Management Studio all tables are visible for the SQL Pool.
Any idea what I might be doing wrong in Azure Data Studio?
It works now.
It seems one has to be careful in which order to resume the SQL Pool (this one is paused most of the time) and connect to the SQL Server.
So first resuming the SQL Pool and then connecting to the server seems to have done it.
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 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.
I have created a publisher (on sql server 2008 r2), create transaction replication and have created a new database on subscriber sql instance (SQL Server 2012 Express).
After I have created a new subscription on SQL Server 2012 Express.
But My new database had't been updated via synchronization.
On server SQL server 2008 r2 via Replication monitor I can see that status is Uninitialized subscription for SQL Server 2012 Express and in details No replicated transactions are available. message
How I can fix it ?
Thanks
The error states that your subscription is uninitialized.
You need to create the initial snapshot. Right-click the publication under the Local Publications folder at the Publisher and click View Snapshot Agent Status. Then click Start. Once the snapshot is generated, synchronize your subscription to apply the snapshot.
This is covered in Create and Apply the Initial Snapshot.
I'm trying to set database snapshot replication using c# with SQL Server 2008 R2. when I'm connecting to the server everything goes as it should... but after the following lines of the code:
distributor = new ReplicationServer(conn);
distributor.InstallDistributor((string)null, distributionDb);
the following error occurs:
This edition of SQL Server cannot act as a Publisher or Distributor for replication. Changed database context to 'master'
Any ideas?
Per Replication Considerations (SQL Server Express), SQL Server Express cannot serve as a Publisher or Distributor, only as a Subscriber. You will need a Standard Edition or higher instance to configure distribution and setup a publication. The Express Edition instance can then serve as a Subscriber.
SQL Server Express cannot serve as a Publisher or Distributor.