Eric M Russell (10/5/2015)

---

Ideally, each application or user account should be a member of a role, and the only additional permissions for each role should be execution on only the...

EdVassie (10/5/2015)

---

If you think that hiding objects will make your system more secure then you are wrong. At best it will give you a warm fuzzy feeling of security,...

Jeff Moden (9/27/2015)

---

andrewbb (9/27/2015)

---

It...

This line of thinking is good. Table structure IS a security risk.

It is good to see some thinking back towards solid n-tier design principles:

Tables

Stored Procedures

Data Access

Business Logical Classes

Application

It is a significant...

This is one feature of System.Persistence, right out of the box.

Texas Technology Commission?

Here's the letter:

September 9, 2015

Texas State Capitol

1100 Congress Ave.

Austin, Texas 78701

Dear Sirs and Madams,

The attached 3 plans are public information and ready for immediate dissemination and implementation:

1.A standard public...

Jayanth_Kurup (9/9/2015)

---

If your looking for comments on the code behind

try catch block and validations come to min.

At database side date format and timezone info could be useful.

You could use...

I forwarded the simplicity of data access to the House and Senate at the state Capitol in Texas. We will see what happens.

I walked the idea around the capitol for a couple of days last week. Trying again in the morning tomorrow.

The Persistence.DLL and some useful SQL Server SPs/Function are attached.

Request for comments, I suppose.

You might have a look at my thread:

http://www.sqlservercentral.com/Forums/Topic1717648-2799-1.aspx

I can send you the Persistence.dll. It makes things much easier.

I think it's a first step. It makes it idiot-proof.

While not applicable every situation, it does handle 90+% of all applications. Since the userID would be the first...