I just wanted to say that it was a not-completely-pleasant surprise to realize that this whole other site for database stuff could be taking questions from SO, and that an area I had earned at least some appreciable amount of reputation in and that I consider my top professional skill (SQL) would no longer be valid there.
My best idea for avoiding this kind of unpleasant surprise to our question-answerers (the one thing, mind you, that makes these sites have any value) is to send a special email to all those with badges (or heck, even any answers at all) in related tags inviting them to the new site and explaining the rationale.
Just like the difference a customer experiences between receiving a large bill and receiving a surprising bill, easing me into it would have saved (at least me, and the people responding to me) stress and heartache, and certainly gotten faster adoption with less resistance.
I realize that had I been super active on SO for the last year I'd have been less surprised, but I wasn't. I have a job and a family and my participation comes in spurts there (to save you time I have almost 5500 rep there earned in 3 years). Here are samples of the kinds of SQL answers I give.
Also, for what it's worth, the "DBA" name was confusing to me as this evokes different things in my mind than the site is intended for, mostly due to my experience in my own company of what DBAs do (not advanced SQL for one thing).
That is all I have to say on that. At least, here, now, on this topic. Great thanks to those who bashed into my head what I could have discovered from diligent searching here on meta.
... those interested in all the gory history of this question and my silly surprise reaction can view the edit history.
One last point I've been thinking about for a couple of days is that people who are not familiar with any stackexchange site (including SO) may find SO first, and ask their SQL questions there, and simply not know to come here. It seems to me that a complete split (all SQL questions here) would be better.
SQL is what I do, and I can't even edit posts yet! Sigh.