I am looking for a way to implement the following security schema in SQL
2005.
Database 1 contains the Raw Data
Data base 2 contains views On the data in Database 1.
We need to create a user who can access in read mode the views in Database
2, but should not be allowed to explore through ODBC connection teh tables
and data in Database 1.
Re: dbdebunk Quote of Week comment ... > a lot of really bad SQL programmers.... But SQL does not have a pointer data type or the ... > being told to design a database.... But why is little Cindy Lou Who employee... (comp.databases.theory)
Re: DBMS and lisp, etc. ... Naively implemented with SQL, again for 10 ... (1 query for the initial orders, 1 query for each order for its ... soon as you upgrade to the SQL database.... (eq (order-customer orderA) ... (comp.lang.lisp)
Re: dbdebunk Quote of Week comment ... > a lot of really bad SQL programmers.... a surrogate key should support the primary key. ... But SQL does not have a pointer data type or the ... > being told to design a database.... (comp.databases.theory)
Re: dbdebunk Quote of Week comment ... But SQL does not have a pointer data type or the ... More and more programmers who have absolutely no database training are ... But why is little Cindy Lou Who employee... (comp.databases.theory)
Re: Just say no to threads [Was: Software architecture] ... they knew there was going to be a database in the app.... Now my colleague just spent a couple/three weeks designing an SQL... Turns out they have a flat file of sample information, ... (comp.object)
