menu

SQL Server in Amazon EC2: Getting Started

Go to Lab

541 Reviews

9c8be10921e0caf94f6450f2f30caba9

I thought my sqlserver instance was corrupt so I went to restart it. However I could stop it but didn;t have permissions to restart it. I thus had to abandon the lab half way through. Disappointing :(

robert d. · Reviewed about 13 hours ago

03ddcc308541d3c09daa04c2a048648a

Brandon H. · Reviewed 2 days ago

8bb8d3c5ff0fe82a7d0907fbe3e5ede1

Vincent L. · Reviewed 3 days ago

7837b29ae8df1457cf8ec803ae164e6a

The password for the RDGW is NOT made clear. It looks like that password is supposed to be the username or something. Very confusing. There is no "Files tab" I searched for several minutes before I found the file under student resources.

Christian H. · Reviewed 6 days ago

D24bcf519d3cee3942e4ff169e890edc

Roger A. · Reviewed 6 days ago

0cd0e9706b30394b78ad7012e266c6c2

Von Paolo M. · Reviewed 8 days ago

Cab0d8862a319f1e9719725abd48029b

dennis a. · Reviewed 10 days ago

4065001d044fa9797daa7aae28bd4367

Ashwin Kumar B. · Reviewed 13 days ago

167491dc92dd8fe1a5bd05820d98b13e

Naveen K. · Reviewed 14 days ago

3c1b0c00404ef6a25717cefa4f68e423

yes

vipul d. · Reviewed 18 days ago

5ecb54449c39ed13322e55784c0bb7ef

most of the time was boilerplate, and not EC2 or AWS specific.

Joshua S. · Reviewed 21 days ago

C37097459859ecd90baacd5e3e3cc3fd

Matt B. · Reviewed 25 days ago

2343a669f7dc9b448145f4e80511014f

mary r. · Reviewed 27 days ago

Fada9bbc89ab27e3907e951485bfdb56

Carlito S. · Reviewed 27 days ago

6872d05abb61da3177ff232307df1593

srinivas m. · Reviewed 29 days ago

90707e53bc4106e91a2ed54f23091ffb

Jonathan H. · Reviewed about 1 month ago

E9f070928106e56895b7a773d4e35582

Tony S. · Reviewed about 1 month ago

Ba92ec757afee38e2d9ce4c509ab8305

2 Very Dis-satisfied to NOT have this lab work and spend that much time. I reviewed the settings twice for the VPC when attempting to connect from the public SQL server to the internal SQL server. No Dice. Ran the Firewall scripts, updated the SQL scripts, etc. This was a routing issue. the system could not connect to the internal SQL server over public IP using MSSQL Management Studio.

norm b. · Reviewed about 1 month ago

79642f26a0b079e8a8beec8f8b2cf290

Dan Kevin B. · Reviewed about 1 month ago

9442712f6370d860488e87a5a57aa542

Patrick M. · Reviewed about 1 month ago

Cda51e5d26b100a7ae9d6e2ba4e36922

Edan B. · Reviewed about 1 month ago

Cda51e5d26b100a7ae9d6e2ba4e36922

Edan B. · Reviewed about 1 month ago

C1488916e7dc74515f732de2c5f71c33

suneel s. · Reviewed about 1 month ago

735818d55f70b2f0486203d8cae369e8

German C. · Reviewed about 1 month ago

B592cfd8daf605f570148d315defaf00

Rodel R. · Reviewed about 1 month ago