4 Framework Special Guide Framework Specific Guidelines 4.1 Data Access Data Access 1. Always use the type of secure data set or data table. Avoid using the original ADO.NET. Always Use Type-Safe Data Sets or Data Tables. Avoid Raw ADO.NET. 2. Always use transactions when accessing your database. Always Use Transactions When Accessing A Database. A) Always use service components transactions. Always Use Enterprise Services Transactions. B) Do not use the ADO.NET transaction. Do Not Use Ado.net Transactions. 3. Always set the transaction isolation level to sequence. Always Use Transaction Isolation Level Set To Serializable. A) Use other isolation levels require management to decide. Requires Management Decision To Use anything else. 4. Do not use the server browser to drag the database connection to a Windows form, an ASP.NET form, or a web service. This is coupled to the interface layer and the data layer. DO NOT USE The Server Explorer to Drop Connections On Windows Forms, ASP.NET FORMS or Web Services. Doing So Couples The Presentation Tier To The Data Tier. 5. Avoid using SQL Server authentication. Avoid SQL Server Authentication. A) is verified using Windows. Use Windows Authentication INSTEAD. 6. The component of SQL Server will be accessed to call the component client. Run Components Accessing SQL Server Under Separate Identity from That of The Calling Client. 7. Always stored in a high-level type secure class package stored procedure. The stored procedure is called only in that class. Always Wrap Your Stored Procedures in a High Level, Type Class. Only That Class Invokes The Stored Procedures. 8. Avoid any logic in the stored procedure. Avoid Putting Any Logic Inside A Stored Procedure. A) If there is if the stored procedure is IF, you may have committed a mistake. If there is an esture, you are doing sometying wrong.
