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.
Related
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.
Actually we have Azure SQL Management instance I got a backup but I cannot restore our VM SQL Server owing this has a SQL Server version less SQL Azure (Azure Team updated SQL Server a couples week ago), so We cannot update QA Server to last SQL Server Version and we need to recovery the backup a soon a possible.
Do you know any way to recover this backup from SQL Azure to this server getting a less version?
Thank you!
You can also use bcp to export the data from Azure SQL Database and then use bcp again or Import/Export Wizard or SSIS to import the data on the SQL Server VM.
You can use Azure Data Factory (ADF) to export tables to your SQL Server VM. ADF will create those tables and copy the data.
In onprem SQL Server you could add a remote database server such as Oracle as a Linked Server, and use in a SQL Server Job Agent job.
Is this possible in Azure SQL Database using Elastic Database Jobs? How?
On Azure SQL Database (PaaS) a concept like a linked server does not exist, however on Azure Managed Instance (PaaS) you can have linked servers but they support limited number of targets. Supported targets: SQL Server and Azure SQL Database. Not supported targets: files, Analysis Services, and other RDBMS (including Oracle).
You may want to consider creating a SQL Server VM on Azure (IaaS) or using Azure Data Factory.
We want to be able to query the Data Warehouse database from the SQL Server database both with the same server name in Azure. Select statements including the database name (e.g. select * from server.dbo.product) returns with error that a reference to the database and/or server name isn't supported in this version of SQL Server. There are articles on creating an external data source in the SQL Server database but we get error that the credentials don't have permission to perform this action.
Azure SQL (as of Azure SQL V12 in late-2016) does not support cross-database queries the same way that they do with a normal on-premises SQL Server (e.g. using the DatabaseName.schemaName.TableName syntax).
Given that Azure SQL and Azure Data Warehouse databases each reside in different physical servers it wouldn't work anyway, as the above syntax is intended for databases that all reside in the same server.
Azure SQL does support cross-database calls via the EXTERNAL DATA SOURCE feature, which we have in normal on-premises SQL Server already. This is documented here: https://azure.microsoft.com/en-us/blog/querying-remote-databases-in-azure-sql-db/
Note that performance won't be that great and you might be better-off doing the querying in your application code. For example complex JOINs which reduce data will run suboptimally.
I am trying to migrate On-premises SQL Server to Azure VM.
I am writing in reference to below link
https://azure.microsoft.com/en-in/documentation/articles/virtual-machines-migrate-onpremises-database/#azure-vm-deployment-wizard-tutorial
I am having multiple applications in which few are hosted in Azure and few are On-premises.
All these applications contact on-premise SQL Server for data manipulations.
In some scenario these applications creates dynamic SQL Agent Jobs!
Now my requirement is to move on-premise SQL Server to Azure cloud. I would like to know how can I manage these dynamic SQL Agents in Azure?
In short, My question is: how can I migrate below items?
SSIS packages associated with these databases
SQL Agent Jobs scheduled in server (created dynamically)
File Stream associated with server databases
Also I am planning to use SQL Server "AlwaysOn" offering. So how to synch these SQL Agent Jobs in these shared Virtual Machines?
I was referring https://azure.microsoft.com/en-us/documentation/articles/sql-database-general-limitations/ and it says as follow
Microsoft Azure SQL Database does not support SQL Server Agent or
jobs. You can, however, run SQL Server Agent on your on-premises SQL
Server and connect to Microsoft Azure SQL Database.
SQL Agents can be dynamically created as shown here https://www.mssqltips.com/sqlservertip/3052/simple-way-to-create-a-sql-server-job-using-tsql/ My question is, will these stored procedures run in azure cloud?
Update
It’s challenge but can be done. We need to setup new Job, which constantly monitors and pull the current role of the replica, based on PRIMARY role, we run the job needs to do if it is the primary.
Below link gives me hint
https://dba.stackexchange.com/questions/45137/sql-server-agent-jobs-and-availability-groups but I am looking for step by step blog/article to achieve this.