Just went through this on both sides. Don't put SEQUEL in your resume unless you're referring to something other than SQL. (And that's not even worth pulling in for an interview from what I've seen.)

Agreed with the other quotes - know your stuff and know the type of position for which you're interviewing. If it's Dev DBA, be prepared to know DB Design and TSQL coding. If it's Prod DBA, know how to troubleshoot. Don't oversell yourself - you'll be found out quickly and generally tossed out. Also, don't be afraid to explain that you don't know something and then explain how you'd go about finding out the answer. That sits a lot better with interviewers than making something up. (However, it's a lot of fun to read those answers when they get posted on a website somewhere. 🙂

Finally, check out some of the other excellent posts/articles from the past on this site. Lots of good information and commentary, some serious, some amusing.

-Pete