DBA or NOT

[Anns via AccessMonster.com]

I need any one's advice/imput on this...PLEASE!

My company will now begin the process of taking all the MS Access (Native
Jet Engines - x30 total in departments) and put the tbles/BE on SQL Server
2005
and the Ms Access FE on MS Sharepoint.

This is the kicker, say 20 out of the 30 (ball park) was created by one
person and that is their whole job function was to create/maintain a QA
tracking system and more.

The person who created the 20 out 30 only knows intermediate ms access and
some vba, but NOT sql or net conversions (visual studio - all the different
languages), so the IT director asks me (I develop in MS Access and
intermediate in VBA and can create web sites using publisher, front page and
HTML) he asks me and this other person if we want to take on the challenge of
helping him and the other IT guy in the conversion process of all of these
db's.

i think asking me and this other person who is NOT qualified
to do this job, he is trying to cut cost, but won't he have to hire a dba in
the end to maintain anyway?

What does this do the developers who developed and still maintain these
current 30 ms access db's, well you guessed it, it now takes all that hard
work that those developers did and still do (they still add more forms,
updates) and it NOW takes the databases owners away from them and grant it
now to the person (s) who will maintain SQL Server 2005 ( I hope will be a
DBA)???

Is this true, once all the databases are converted, the owners will no longer
be able to go behind the scenes in tables, queries,etc.... It will now be in
the hands of a DBA?

You know the funny thing is the IT Director wasn't even sure if he was going
to hire a DBA, who in the heck will maintain all of those db's on the server?
There is only one other guy and he certainly does not have the training or
skills or TIME.
when these conversions take place like this at a company, most of the time
the
ms access dbs that have now been put into sql will now take the ownership
away
from the owner (they cannot develop no more, unless they are sql friendly/dba)

and put all of that into one persons hand (DBA) to maintain and development???

???

Is this true, when these conversions happen, the original owner of the db's
(not sql friendly) will no longer be able to develop b/c it will need to be
done now by a DBA or related experience? Basically one person managing all of
those db's on the SQL SERVER?

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200606/1

[Rick Brandt]

Anns via AccessMonster.com wrote:

I need any one's advice/imput on this...PLEASE!

My company will now begin the process of taking all the MS Access
(Native
Jet Engines - x30 total in departments) and put the tbles/BE on SQL
Server 2005
and the Ms Access FE on MS Sharepoint. [snip] What does this do the developers who developed and still maintain
these current 30 ms access db's, well you guessed it, it now takes
all that hard work that those developers did and still do (they still
add more forms, updates) and it NOW takes the databases owners away
from them and grant it now to the person (s) who will maintain SQL
Server 2005 ( I hope will be a DBA)???

Is this true, once all the databases are converted, the owners will
no longer be able to go behind the scenes in tables, queries,etc....
It will now be in the hands of a DBA?

[snip]

Depends on your situation. When all of my stuff went from Access to SQL
Server (years ago now) I became the DBA for all of my tables on the SQL
Server. Later when we started using UDB400 as well then I became a DBA on
that box as well. I still have cradle to grave responsibilities for all of
my tables and associated server objects.

In many companies this is left to dedicated DBA personnel, but it doesn't
HAVE to be done that way.
--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com