Re: Understanding SQL and Microsoft GP



Typically, finance people do not have the sa password - nor should they. A
DB server is to be maintained by a qualified DBA. Access can be granted on
a granular basis. For example, you could be given DBO (database owner)
rights to the GP DB, but absolutely no other rights within SQL Server.

Your IT people probably don't need to be trained on GP in order to support
the DB side of things. All they would be interested in would be backups,
index maintenance, etc.

--
Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau


"hupton" <heather@xxxxxxxxxx(donotspam)> wrote in message
news:69DA620E-B363-4C72-8983-2CDE8254F062@xxxxxxxxxxxxxxxx
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: file rights issue...
    ... Domain Admin has rights to everything so not being able to access the ... The Terminal Server is an entirely different ... of BV we are running uses an SQL DB engine called Pervasive SQL to ... the accounting data on the Windows 2000 server through the pervasive ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: file rights issue...
    ... files over to the WIn2K machine where domain rights are now being applied. ... The Terminal Server is an entirely different issue. ... BV we are running uses an SQL DB engine called Pervasive SQL to access ... Windows 2000 SQL server - which is also where the accounting data is ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: file rights issue...
    ... of the domain so no domain rights were being used - just the local NT ... The Terminal Server is an entirely different issue. ... of BV we are running uses an SQL DB engine called Pervasive SQL to ... our Windows 2000 SQL server - which is also where the accounting data is ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: file rights issue...
    ... part of the domain so no domain rights were being used - just the local ... The Terminal Server is an entirely different issue. ... of BV we are running uses an SQL DB engine called Pervasive SQL to ... our Windows 2000 SQL server - which is also where the accounting data ...
    (microsoft.public.backoffice.smallbiz2000)
  • REPOST:SQL Login with no Fixed Server Role and DB Role can stop SQL Agent Service?
    ... I had checked all the user rights, and everything seems to be proper...but ... running SQL 2000 Enterprise Edition on ... Windows 2000 Server. ... SQL Server on his Enterprise Manager using this SQL Login. ...
    (microsoft.public.sqlserver.security)