Questions tagged with Microsoft SQL Server
Content language: English
Sort by most recent
We recently upgraded an MSSQL RDS database instance from 12.00.6329.1.v1 to 15.00.4236.7.v1. The instance functions fine, but it is supporting a legacy application that sometimes encounters errors that leave us no choice but to rollback to a snapshot. We also copy snapshots to our QA account periodically to refresh our QA databases, and this procedure has increased by the same significant amount of time. Prior to upgrading, these snapshot restores took around 30 minutes to get the instance to the Available state. After upgrading, it is taking several hours. The most recent attempt took 6 hours. This is harmful to our business as the increase in recovery time causes cascading effects. This feels like a possible AWS bug, I'm not sure what we could possibly do differently to improve this outcome. Any ideas?
Instance details:
Instance class: db.r6i.4xlarge
Storage type: gp2
Storage size: 2000GiB
Hi,
We have SQL 2017 ENT running on EC2 instances (i3.4xlarge) in Ireland. We are using Litespeed to do full and log backups to S3 in the same region.
This is a very large Database. Through litespeed we are doing maximum compression and stripping the full backup to 7 files and each file size is ~430 GB.
In the SQL server side, full backups are scheduled to always run in AG secondary replica, so it is only doing the backup work load nothing else.
A full back usually completes in ~ 16 to 18 hours. But sometimes the full backup takes 30 to 40 hours and sometimes in worst cases it is taking 60 to 75 hrs to complete.
For the slow running backups, at the moment we dont have a clue on where things are actually slowing down.
One thing I notice from the litespeed backup summary - whenever backup throughput reduces, the backup time increases proportionally.
How would I go about troubleshooting this to find out the root cause and what actions should I take so that full backup always completes in less than 20 hours?
Thanks in advance.
We are processing a cube on a Microsoft SQL RDS SSAS installation and it's failing for the below:
Failed to save modifications to the server. Error returned: 'OLE DB or ODBC error: Query timeout expired; HYT00.
OLE DB or ODBC error: Operation canceled; HY008.
This can be fixed by changing the ExternalCommandTimeout and ExternalConnectionTimeout analysis server properties. I tried doing it through SSMS and a XMLA script and got access denied messages. Is there a way to adjust these properties for a managed Microsoft SQL server SSAS RDS instance?
We have been able to connect to a Microsoft SQL Server DB using both Glue's DynamicFrame and Spark's own JDBC write option due to the Glue connection option. However, considering the transactional nature of the data, we wanted to switch this to sending data programmatically using a python library, thus allowing us to move from Glue ETL Job to Python Shell Job. Our initial option was pyodbc, however, due to our inability to integrate the required driver with Glue, we were unsuccessful. Another option that we looked at was pymssql. Our experience with connecting to Microsoft SQL server using pymssql was seamless. However, it was restricted to Python 3.6 and we were unable to import it with Python 3.9. Our requirement for Python 3.9 was due to the boto3 version compatibility with the said python version as we are also trying to access the boto3 redshift-data client in the same script. Having considered all of the above, is it possible to query Microsoft SQL Server using a python library with Python 3.9 in AWS Glue Python Shell Job?
For the last few days, I am trying to upgrade an RDS SQL Server web-edition instance from db.t2.small to db.t3.small. but every time i receive the following error.
*We're sorry, your request to modify DB instance xxx has failed.
Cannot modify the instance class because there are no instances of the requested class available in the current instance's availability zone. Please try your request again at a later time.*
I have also used AWS CLI to check the orderable db-instances
describe-orderable-db-instance-options
This returns command also shows that orderable instances are available in us-east-1 with instance type as db.t3.small , but still i am unable to change the instance type. Is anyone facing the same issue or has a solution to this ?
I just recently changed email provider from privatemail.com to microsoft. my domain stayed on namecheap but i changed the dns record so messages go directly to microsoft now. Now i received a message from amazon saying dkim signin was disabled for this domain in dns records i dont know if this has to do with the fact that i cannot login to sendy.co but i copied and pasted back the 3 Cname records back in name cheap..
Can somebody help me out with this, i need to investigate how i can log back in to sendy.co with my domain and login
Thank you
On updating the MSSQL package from Version6.2.0 to Version9.1.0 in package.json file , we are facing the below error .
Failed to connect to Server1_name - Hostname/IP does not match certificate's altnames: Host: Server1_name is not in the cert's altnames: DNS:Server2_name
The lambda is written in Node.js, lambda connects to mssql server in npm mssql version 6.2.0 but throws the above error in npm mssql version 9.1.1
We upgraded the version for resolving the security vulnerability reported for dependency package (xmldom).
Please guide what can be the ways to resolve the error and the root cause.
created a RDS and default user is admin backup is in s3 and added option group for SQLSERVER_BACKUP_RESTORE ,iam role also but when i run the restore command i.e exec msdb.dbo.rds_restore_database @restore_db_name='backupdb',
@s3_arn_to_restore_from='arn:aws:s3:::Bucketname/backupfile27022023.bak';
its showing an error as The EXECUTE permission was denied on the object 'rds_restore_database', database 'msdb', schema 'dbo'.
admin is master user but it doesn't have the execute permission. How to solve it
I have an RDS instance, with MS SQL Server database.
I need to grant permissions to a user in my application to execute some important procedures.
However, even connected to the RDS instance with the admin user, I cannot grant these permissions.
The query I need to run is the following:
```
USE [master]
GO
sp_configure 'Advanced Options', 1
GO
RECONFIGURE
GO
sp_configure 'Ole Automation Procedures', 1
GO
RECONFIGURE
GO
GRANT EXECUTE ON sys.sp_OACreate TO [usr_apis]
GRANT EXECUTE ON sys.sp_OADestroy TO [usr_apis]
GRANT EXECUTE ON sys.sp_OAGetErrorInfo TO [usr_apis]
GRANT EXECUTE ON sys.sp_OAGetProperty TO [usr_apis]
GRANT EXECUTE ON sys.sp_OAMethod TO [usr_apis]
GRANT EXECUTE ON sys.sp_OASetProperty TO [usr_apis]
GRANT EXECUTE ON sys.sp_OAStop TO [usr_apis]
```
and when running the query above, the following errors are returned:
```
Msg 15247, Level 16, State 1, Procedure sp_configure, Line 105 [Batch Start Line 2]
User does not have permission to perform this action.
Msg 5812, Level 14, State 1, Line 5
You do not have permission to run the RECONFIGURE statement.
Msg 15247, Level 16, State 1, Procedure sp_configure, Line 105 [Batch Start Line 6]
User does not have permission to perform this action.
Msg 5812, Level 14, State 1, Line 9
You do not have permission to run the RECONFIGURE statement.
Msg 15151, Level 16, State 1, Line 11
Cannot find the user 'usr_apis', because it does not exist or you do not have permission.
Msg 15151, Level 16, State 1, Line 12
Cannot find the user 'usr_apis', because it does not exist or you do not have permission.
Msg 15151, Level 16, State 1, Line 13
Cannot find the user 'usr_apis', because it does not exist or you do not have permission.
Msg 15151, Level 16, State 1, Line 14
Cannot find the user 'usr_apis', because it does not exist or you do not have permission.
Msg 15151, Level 16, State 1, Line 15
Cannot find the user 'usr_apis', because it does not exist or you do not have permission.
Msg 15151, Level 16, State 1, Line 16
Cannot find the user 'usr_apis', because it does not exist or you do not have permission.
Msg 15151, Level 16, State 1, Line 17
Cannot find the user 'usr_apis', because it does not exist or you do not have permission.
```
How can I grant the user of my application the necessary permissions to execute these procedures?
Thanks.
asked 22 days ago
We should upgrade the standard Microsoft sql server instance from 2017 version to 2019 version.
What is the best procedure to follow in order not to lose data
I have an AWS RDS Mssql and On-premise Mssql, Both servers have 4 CPUs and 16 Memory. Both servers have the same data in the table about 700k records.
When the exec query selects 1000 records first.
AWS RDS Mssql: ~2.4 seconds
On-premise Mssql: ~ 0.5 seconds.
Why is AWS RDS Mssql too slower than On-premise Mssql?
I am trying to use DMS to capture change logs from the SQL server and write them to S3. I have set up a long polling period of 6 hours on MSSQL CDC Capture job. (AWS recommends > 1 hour). DMS fails with the below error when the database is idle for a few hours during the night.
DMS Error: Last Error AlwaysOn BACKUP-ed data is not available Task error notification received from subtask 0, thread 0
Error from cloud watch - Failed to access LSN '000033fc:00005314:01e6' in the backup log sets since BACKUP/LOG-s are not available
I am currently using DMS version 3.4.6 with multi-az.
I always thought the DMS reads the change data immediately after updating the T log with the DML changes. Why do we see this error even with a long polling period? Can someone explain why this issue is caused? how we can handle this ?