tag:blogger.com,1999:blog-7958569345934714789.post2853586277053946777..comments2009-08-05T20:52:34.388-04:00Jeff Stevensonnoreply@blogger.comBlogger1125tag:blogger.com,1999:blog-7958569345934714789.post-13841229402760090442009-08-05T20:52:34.388-04:002009-08-05T20:52:34.388-04:00

Jeff, I've always been curious about the default security setup in SQL. In Oracle we have the same issue, but there's no easy solution because you can't effectively remove an Oracle account from PUBLIC. What I ended up doing on the Oracle side is writing a security utility that sniffs the E1 database and removes the PUBLIC privileges. It amazes me how many clients don't ever

Slownsteadihttp://www.blogger.com/profile/11089521522737443033noreply@blogger.com