Experience in DB testing does not necessarily imply developer-level skills. Quantifying what your team's skillset will help you make decisions. Since this is an established team it might be good to have a look at what they currently produce in terms of deliverables (source control repository?) and ask for any 'process and procedure' documentation the group currently adheres to. If the group is following a specific test methodology then they're already in the game. Knowing the toolset will help shape the approach so I would begin the process of learning that as soon as possible. Most of the DB unit test tools lay out a preferred methodology to follow.