Azure SQL Restore Failed - Status Conflict (Details show Internal Server Error) - azure-sql-database

I am restoring to a point in time, as a BCP test and it has failed. This is being done in the portal to a new database name that does not exist. It is not in an elastic pool. It tries to deploy and the new database shows up in SQL Management Studio as restoring. It then disappears and the portal shows as failed after running for a couple of hours on a DB of a few hundred MB.
I have tried another db and the same issue is present. They are all DTU based.
The statis is shown as conflict, and the detailed error is shown as Internal Server Error.
Steve.

I created database in Azure portal and click on the restore at overview of database
Image for reference:
I click on the Review+Create button I got the same error
as you got
Image for reference:
I repeated the steps for restore the database which I have done above and changing time the database is restored successfully.
Image for reference:
Restored database:

Related

Sql Database sync error in azure Database Sync Group

I'm trying to connect my local database with online database. I've followed the full procedure but Database Sync Group is showing a log error of following type
Database provisioning failed with the exception "SqlException
Database provisioning failed with the exception "SqlException ID: ebcc6489-1083-4635-aa5e-a34deecb61c1, Error Code: -2146232060 - SqlError Number:18456, Message: Login failed.
For more information, provide tracing ID ‘3b685498-b462-4bde-b99b-0f1a156369c7’ to customer support."
Moreover hub database is not showing any table to select for sync but sync agent database is showing up.
Kindly please help me out.
Try to verify the SQL login you used to configure the hub database on the sync group has been disabled or the password has been changed.
On the Azure Database, provide the SQL Admin login with its current password. If you have provided this information before try to do this again.
Follow these steps:
Click on the Azure DBClick “Sync to other database”
Click on the sync group which you have created.
Click on the databases.
Click on your hub server.
Enter your username and current password.
Try to sync.
Reference: Configure SQL Data Sync

The connection either timed out or was lost- Error while cube synchronization from source server to destination

I am executing XMLA script via scheduled SSIS dtsx package to synchronize the ssas cube form source to destination server. Everytime it works fine but sometimes it gives error in random manner like once in 2-3 months. Error is : "The connection either timed out or was lost"
Later when I perform synchronization manually it works. I checked from network between 2 server, configuration , data related settings and also from memory perspective, but everything seems fine.
Can you please guide how to tackle this?

Microsoft Azure: There was an error while creating data connection 'SQL data connection'. Deployment to resource group failed

I am trying to create an Android Mobile app via the Azure app service and while doing so, I am trying to create a database, but I am getting the error 'there was an error while creating data connection 'SQL data connection'. Deployment to resource group failed'. Please help as soon as possible.
$
This error is due to server limit exceeding the quote associated with your account. Under all resources, check if there's a new SQL server created with a random name- you will need to delete that. Attempt to create again.
(just done- it worked!)
I've faced the exact issue.
First time it failed giving the error - Data Connection Creation Error..!
When Configuring for the first time it didn't work for me.
i.e.,
Creating a Database
Creating a New Server
Entering Server Admin Login
Entering Server Admin Password
I've noted down all the above information.
Tried Second time setting up the Connection String with the above details IT WORKED.
Hope this information helps.

Copy database fails with SQL Agent not started error, but it is running

I'm trying to copy a database to another server. I've successfully done this with these two servers several times, the last time was just a few days ago. However, now when I try to execute it, I get an error:
TITLE: Copy Database Wizard
------------------------------
Start failed for Job 'CDW_xxxx_SGSTG51DBA01_13_2'.
------------------------------
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch
(Microsoft.SqlServer.ConnectionInfo)
------------------------------
SQLServerAgent is not currently running so it cannot be notified of this action.
(Microsoft SQL Server, Error: 22022)
Base on this information, I immediately checked that SQL Agent was running. It wasn't, so I started it. I ran it again, but got the same error. I then double checked that the login information provided for both the source and destination servers was correct. It was.
So I'm now getting this error with verified connection information and SQL agent is running. What else could be causing this problem? Does the account running SQL agent need access to both servers?

My job is running but no data is comming

I have got a ssis package which runs when I manually run from Integration Services. But when I try to run it from a job. Then it runs but no data is seen in the data. There seems to be some permission issue. Can somebody tell me what permissions are required for running a package from a SQL Server Job?
State the error message.
If you are using a flat file connection manager, and that's where the error is occurring, click 'start' then 'computer' then check to make sure you are mapped to that drive. If not, click the tab upper right corner to map to the drive then when you access the file through SSIS you shouldn't have an error.
If the package runs successfully as a job using the SQL Server Agent then you have the permissions set right for the database side.
However make sure if you are accessing any external data such as flat files that the agent is able to access these locations. You may have permissions on your Windows account to access the locations when you run the package in Visual Studio but the agent service running the job requires those permissions too.
If this is not the case can you clarify what your package does and any messages you receive from the catalog reports so I can help further.