I’ve always personally used dedicated servers and VPS so I have full control over my SQL Server (using 2008 R2). Now I’m working on a asp.net project that could be deployed in a shared hosting environment which I have little experience with. My question is are there limitations on the features of SQL Server I can use in a shared environment?
For example, if I design my database to use views, stored procedures, user defined functions and triggers, will my end user be able to use them in shared hosting? Do hosts typically provide access to these and are they difficult to use?
If so, I assume the host will give a user his login, and he can use tools like management studios to operate within his own DB as if it were his own server? If I provide scripts to install these, will they run on the user’s credential within his database?
All database objects are available. It includes tables, views, sp, functions, keys, certificates…
Usually CLR and FTS are disabled.
At last, you will not be able to access most of the server objects (logins, server trigger, backup devices, linked servers etc…)
SQL Mail, Reporting Services are often turned off too.