• Replies 3 replies
  • Subscribers 338 subscribers
  • Views 116 views
  • Users 0 members are here
Related

Tessitura database in AWS

Justin Snair
$organization

Just curious if anyone has tried running the Tessitura database in the RDS managed MSSQL server in AWS?   We have Tessitura running in AWS for DR but still have EC2 instances running MSSQL for the database.  Looking toward moving this into production but would rather use a hosted database solution for high-availability and peace of mind. I know there will be issues with SSRS, SSAS and SSIS but we run those on separate instances already  so we can continue to do that in the cloud..

I also plan on testing this myself but just wanted to get some feedback if anyone else has tried yet.

Parents
  • $organization

    I haven't tried running Tessitura DB on AWS RDS but when I have used RDS solutions I have always had to work around the fact that I don't have full SA rights, which although not major does catch you out occasionally.

    I don't believe you have access to the file system from the DB (I may be wrong as never needed to interact with it) which for Tessitura you will need as Extractions as that requires access for outputting the files and Report Server I believe uses file system to tell the DB to send the PDF(file) as an attachment.

    Also not sure how the assemblies work for CLI, I know the wordfly one requires a DLL on the DB File system for it to be installed. They are used by the Tessitura Client to send Forgotten password and order confirmation emails as 12.5.1 still uses SOAP API to send those.

    Mark

  • $organization in reply to Mark Ridley

    The loss of SA access would certainly be a shock to some people but as you mention is easy enough to work around.  I hadn't thought about the access to the file system.  Is there anyway to change the location of where those extractions and reports are sent (shared location maybe) rather than having them stored on the database server directly?  You definitely do not have access to the filesystem when using RDS.

     

    I am not concerned with SOAP at all for this as we would be deploying this as v14+ after our website has fully updated to REST.

     

    Thanks for the advice.

Reply
  • $organization in reply to Mark Ridley

    The loss of SA access would certainly be a shock to some people but as you mention is easy enough to work around.  I hadn't thought about the access to the file system.  Is there anyway to change the location of where those extractions and reports are sent (shared location maybe) rather than having them stored on the database server directly?  You definitely do not have access to the filesystem when using RDS.

     

    I am not concerned with SOAP at all for this as we would be deploying this as v14+ after our website has fully updated to REST.

     

    Thanks for the advice.

Children
  • $organization in reply to Justin Snair

    By not full SA access this is the quote from Amazon

    In order to deliver a managed service experience, Amazon RDS does not provide shell access to DB instances, and it restricts access to certain system procedures and tables that require advanced privileges.

    Note
    When working with a SQL Server DB instance, you can run scripts to modify a newly created database, but you cannot modify the [model] database, the database used as the model for new databases.

    Extractions output folder can be changed to be a shared folder.

    Was more the fact that the output was triggered from the database using the cmd shell that runs bcp, so it may be possible to output to an S3 bucket but not something I have tried. Have never checked whether it will allow you to access the cmd shell.

    Mark