Understanding SQL and Microsoft GP

I am trying to get and understanding of the security with SQL and GP.
Unfortunately, I know alot about GP but virtually nothing of SQL. Our IT
person handles the SQL side. The confusion I am running into with with some
of these new tools with GP10 there are rights you have to have to deploy
these things. I am not allowed access to SQL only what I have through access
to GP. My IT person says that we cannot have any rights to SQL because that
would open us up to the entire database. We are housing more than just GP
databases on the SQL2005 Server. Are we mising something with security to be
able to effectively utilize more tools/functionality with GP? I hope this
makes sense. We have not upgraded to 10 yet but will be mid-September and I
would like to get some clarification about security. I do not have the SA
password. Do other companies allow someone in the finance department (we are
the main users of GP right now) have that SA distinction. Sorry for the
length but I am trying to understand this very confusing issue. Our IT
people have not been trained in the realtionshop of SQL and GP. They only
have the SQL knowledge. I feel we have a communication gap. Any suggestions?

.

Relevant Pages

  • Re: Which database should I use?
    ... > and alter the database. ... That is exactly what is possible with SQL server and for a fact with all ... other RDBMS systems but not with Access in combination with a Workgroup ... >only weak point is on security. ...
    (microsoft.public.dotnet.languages.vb)
  • Re: External .mdb inside Forms
    ... > You can set a form's recordsource or a combo box's rowsource to a SQL ... > Note that this method can be used if the external database is secured ... > security, but this is fundamentally insecure and I don't think there's ...
    (microsoft.public.access.forms)
  • Re: Multiple Database Security - How to handle
    ... There is no 'execute as' in SQL Server but you can simplify security ... Assuming the DM database contains tables that are accessed only by ...
    (microsoft.public.sqlserver.security)
  • Re: Microsoft Access Security Best Practices when linking to a SQL back end
    ... Before Access can verify the username and password in the SQL ... Access authenticates the user before the database actually opens. ... own security algorithm is not going to be an easy task. ... > was originally written to use access's own .mdw file for security. ...
    (microsoft.public.access.security)
  • Re: Putting/retriving files into a database
    ... Also, *never* put user-supplied input in an SQL ... attention to what it says about SQL Injection in the "Database ... Security" section. ... Study the "Handling File Uploads" chapter in the PHP ...
    (comp.lang.php)