If your Class involves a typical “Client/Server” Application, when creating a Lab Template, you will likely need a “server” for your application, AND some sort of “database”.
It IS possible to include a “database” resource and have it automatically installed and available to your “server”, OR you could just load the database on your server (template) yourself.
This article will go over the considerations related to attaching a database as a (cloud) resource, vs. installing your own.
In the Lab Template Designer, there are 4 ways to include a database:
- Add an explicit "database" resource along with your "server" resource in 1 Library
- Install your database engine (i.e. SQL-Server, MySQL, etc.) on your "server" (1 "server" resource in your Library containing your Application and Database)
- Include an additional "server" node to your Template and communicate between the App-Server node and the Database-Server node (1 Library with 2 server nodes).
- Create a separate Database Library with one "server" communicate between the App-Server library and the Database-Server library (2 separate Libraries, one for App-Server, one for Database).
The following server-level roles are not currently available in Amazon RDS:
bulkadmin
dbcreator -
diskadmin
securityadmin
serveradmin
sysadmin
Due to these limitation, you may want to load SQL-Server MANUALLY (with your local license).
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article