Questions tagged with Microsoft SQL Server
Content language: English
Sort by most recent
On RDS for SQL Server, I understand that restores from EBS snapshots use lazy loading when downloading data from S3.
If I restore a native backup file (.bak) from S3, will this use the same lazy loading as with snapshots or is all the data available on the instance once the restore is completed?
Is lazy loading a feature of snapshot restores only?
I am using AWS RDS Performance Insights and am trying to establish who and what is generating DB load, when viewing 'Slice By User' I see the expected username of the DB connection cross-referenced with the host I am expecting, but I also see a large amount of load coming from the host generated by a user labelled as 'Unknown'.
I am using SQL Server DB.
Has anyone else experienced this or is able to explain why I would be seeing this behaviour?
Thanks for any help
We're using DMS for CDC Only migration for the time b/w point in time restore and current DB state, i.e AWS DMS to replicate changes as of the point in time at which you started your bulk load to bring and keep your source and target systems in sync.
We've configured AWS DMS (CDC Only) with source endpoint to On-premise SQL Server 2012 (Standard Edition) and Target endpoint with AWS RDS MSSQL 2019 (Standard Edition). By looking into AWS CDC pre-requisites documentation https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Source.SQLServer.html#CHAP_Source.SQLServer.Prerequisites
Running below query on on-premise MSSQL 2012 instance returns an error, ref: https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Source.SQLServer.html#CHAP_Source.SQLServer.Prerequisites
```
use uat_testdb
EXEC sys.sp_cdc_enable_db
```
Msg 22988, Level 16, State 1, Procedure sp_cdc_enable_db, Line 14 [Batch Start Line 0]
This instance of SQL Server is the Standard Edition (64-bit). Change data capture is only available in the Enterprise, Developer, and Enterprise Evaluation editions.
It looks ongoing replication CDC feature is supported only from MSSQL standard edition from 2016 SP1 and later.
Could you please suggest if there any other workaround to complete CDC without upgrading our on-premise MSSSQL Standard Edition 2012 to Std Edition 2016 / Enterprise Edition?
**However, without applying this CDC prerequisites config settings at on-premise DB instance, we can see the ongoing and replication b/w on-premise and RDS DBs instances statistics that shows sync updates of Inserts and Deletes. (Based on the testing target RDS DB instance sync. happening only for Insert and Delete operations of on-premise source db not for any updates)
Could you please confirm/clarify if those CDC pre-requisites config are mandatory since we could see the replication successfully on DMS and why we're not getting any error /warning messages on AWS DMS for missing CDC prerequisites config. settings? Thanks.**[]()
hi, It shows me the error 'the provided token has expired' when creating the backup from sql server to send it to S3. I followed the steps of the official guide
Can AWS Backup be used to backup an Amazon RDS managed Oracle or MS-SQL database?
Can we directly transfer or copy data from Sql Server on premises to Snowflake with help of AWS Glue?
Need to know if it is possible and feasible to do ETL with help of AWS Glue from SQL Server DB on premises(JDBC Connector used ) to Snowflake(JDBC Connector)?
Curious to know about, can we use AWS Glue to migrate 24 TB data from MS SQL Server(On-prem) to S3?How much time will it take (average) and how much effective it would be from other options? And would it be costly from other options of data transfer(like AWS DataSync, Snowball)?
Hi, Has anybody ever done a migration of SQL Server from RDS to on-prem or EC2 SQL? I'm struggling to find a way to migrate the databases across. Any pointers would be much appreciated.
We had scheduled, daily auto back-up of our SqlServer Db on RDS, to S3 bucket for at least last 6 years. It was working fine since then. Suddenly it stopped working, which means we don't see any Backup in our S3 bucket since 24th March. Up on diagnosing the problem, we realized that it is failing since then and the error is
STEP1
exec msdb.dbo.rds_restore_database
@restore_db_name='RestoreDbFromS3',
@s3_arn_to_restore_from='arn:aws:s3:::awsbucketName/SqlServerDb.bak';
STEP 2
exec msdb.dbo.rds_task_status @task_id=7;
Response indicates Error with following Task Description
[2022-05-28 12:51:22.030] Task execution has started.
[2022-05-28 12:51:22.237] Aborted the task because of a task failure or an overlap with your preferred backup window for RDS automated backup.
[2022-05-28 12:51:22.240] Task has been aborted
[2022-05-28 12:51:22.240] The provided token has expired.
We studied a lot to identify the root cause and solution but could not find anything accurately relevant.
https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/SQLServer.Procedural.Importing.html#SQLServer.Procedural.Importing.Native.Troubleshooting
above link shows troubleshooting options as per the error responses, but this does not include the error response that we are getting.
Note: between 25th & 26th March, our aws instance was suspended for couple of hours due to delayed payment of monthly invoice. we restored the same quickly. Everything on the same aws account is working fine since then, but we just found out that db backup service has impacted as we see the last successful backup available in S3 bucket is of dated 24th March.
We suspect that some token has expired up on account suspension, but are unable to identify which one and how to restore the same back to normal.
Help, Assistance and Guidance would be much appreciated.
Everything is set for the backup of RDS to S3. But when executed :
exec msdb.dbo.rds_backup_database @source_db_name='altahrirVersion', @s3_arn_to_backup_to= 'arn:aws:s3:::mumbaisqlserverbakup1/back1.bak', @overwrite_S3_backup_file=1;
the % complete remained as 0% till next day
Then I used:
exec msdb.[dbo].[rds_cancel_task] @task_id= 1
the task now shows: CANCEL_REQUESTED and 0%
Now i am stuck. I cannot create a new backup or cancel the standing one!
Please help me Thanks
Sorry, I've been working at this for the past 4 hours...
Created an RDS SQL Server Express DB via "Easy Create" options.
I modified config after to allow public access.
I'm not able to connect via Visual Studio Code "mssql for Visual Studio Code" extension.
"mssql: Error: Unable to connect using the connection information provided."
I'm also not able to ping, telnet et cetera the endpoint plus 1433 port. That bit doesn't completely surprise me - I've seen posts stating Amazon blocks that type of traffic.
Database is associated with default VPC which is wide open - no defaults changed.
Under "Security Groups" for database I see "Security group rules (2)" which leads me to believe there are 2 groups associated but the list below is completely blank and I cannot edit - add, delete, modify. My thought it those groups are hidden since it's managed.
Any ideas?
Thank you!