Viewing 15 posts - 1 through 15 (of 479 total)
Typically a colleague has just found the issue after a few hours looking at this issue. The project properties for the solution had the "TargetServerVersion" field set to "SQL server...
November 21, 2018 at 7:53 am
One other nugget of information which strikes me as odd, if we import the package into SSIS the script task is populated with our custom code to set the connections, ...
November 21, 2018 at 7:37 am
The only viable workaround at the moment is using package configurations for the...
November 21, 2018 at 7:28 am
November 21, 2018 at 7:26 am
This is very interesting as its something we are actively looking at right now.
August 29, 2018 at 9:30 am
If its the SQL server timing out then it should also appear in the SQL server Log, there may be further information which can help debug, if its just the...
July 12, 2018 at 8:35 am
Typically when I have had semaphore timeouts it has been due to CPU pressure on the resource, have you checked the CPU usage stats on the RDS instances and the...
July 12, 2018 at 3:08 am
Where are you running the redgate software? Are you running on an EC2 instance in one of those regions or from on premise?
July 11, 2018 at 7:29 am
I am looking at deploying a SQL Standard Cluster in AWS using SIOS DataKeeper. Anyone...
July 9, 2018 at 8:04 am
As much as it was a very long time ago, it was indeed the source of our issue, once we removed the duplicated articles the issue never came back.
June 7, 2018 at 6:09 am
One option is to write the backups (full \ log) on a local EBS volume and subsequently push them to S3. It will make restoration slightly more complex than just...
May 16, 2018 at 8:17 am
Yeah you do, I'm not sure why it doesn't cover it as it would have made sense to.
April 26, 2018 at 7:25 am
I had similar issues when setting this up on SQL 2017. This may be of some help to you:
April 25, 2018 at 8:38 am
April 23, 2018 at 4:56 am
April 11, 2018 at 3:07 am