The way to go for your database implementations
Rating: 10 out of 10
September 12, 2019
GD
Vetted Review
Verified User

24 years of experience
I use Microsoft SQL Server primarily as the back end database server to ASP.Net C# websites. For authentication and authorization, the database uses tables and stored procedures to implement membership or identity for user login and defining roles. Of course, the database is used to hold data entities for the needs of the website. Use of stored procedures, views, and sequences full-text indexing are just some of the useful features I take advantage of.
- Speed of selects with appropriate indexes.
- Use through C# of Linq queries to the data.
- Ability to use CLR assemblies to program in C#.
- Replication to keep the database mirrored to another server.
Cons
- I sure wish the T-SQL language was more like C# - it's really primitive.
- I would like an easy way to pass an array to stored procedures and a way to iterate through the array in the code.
- Integrated source control for the database would be appreciated.