InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comTue, 21 May 2013 16:59:49 GMT20http://www.sqlservercentral.com/Forums/Topic1392541-392-1.aspx[quote][b]komal145 (12/7/2012)[/b][hr]I know , it's kind of DBA questions and they are excepting the Developer to answer it and I am a Newbie to SQL server ,and never faced such situations in realtime enviornment.[/quote]Yes these are real life scenarios that a DBA faces and the questions asked to you sound more like a discussion rather than questions. They were probably trying to figure out what all you can think in a specific scenario. No answer is totally correct or totally wrong but they usually see how you think and whether you jump on conclusions straightaway.If you are interested in an admin position and were not happy with the outcome of the interview, don't feel bad. Learn some SQL first. Be in position to understand simple procedures, functions etc. Read a lot to learn about scenarios. Then side by side, learn about admin stuff like taking backups, keeping log files intact on DEV server. This will make you ready for a junior DBA position. Discuss with the DBA about the things that you learn recently. When you slowly are in touch with some DBAs, you might well be inducted into their groups to recieve some alerts. Try to find common patterns, send your understandings to the DBA.At some point of time in your career, someone will definitely pick your enthusiasm and that will be your first breakthrough. Don't give up and the best thing is to read and collect a lot of information.All the best!ChandanMon, 10 Dec 2012 05:03:37 GMTchandan_jha18http://www.sqlservercentral.com/Forums/Topic1392541-392-1.aspxIf they are looking for a junior developer you *may* be ok, but I am hard pressed to believe you are ready to become a DBA which is one the most highly trusted positions in an organization. I agree with Jeff, take time to get the knowledge and experience then you can be ready.CEWIISat, 08 Dec 2012 13:46:58 GMTElliott Whitlowhttp://www.sqlservercentral.com/Forums/Topic1392541-392-1.aspx[quote][b]komal145 (12/7/2012)[/b][hr]I know , it's kind of DBA questions and they are excepting the Developer to answer it and I am a Newbie to SQL server ,and never faced such situations in realtime enviornment.[/quote]It depends. These types of questions can mean different things based on the postion beig offered. I assumed they were meant for a DBA position. For a T-SQL Developer position, the answers may change a bit but the questions are still quite valid.I'm with Gail, though. Did you explain that you were "new" to SQL Server before the interview? And what was the position actually for? Developer or DBA?Fri, 07 Dec 2012 17:08:03 GMTJeff Modenhttp://www.sqlservercentral.com/Forums/Topic1392541-392-1.aspxSorry to be blunt but if you're asked these question in a job interview and you cannot address them (after some followup questions because some of them are vague), than this is probably not the job for you.As pointed out above, some of the questions are about broad topics that are not best addressed in a forum reply. If you are interested in learning these topics, you can look through the Articles section of this site, where some of these topics are described in great detail.Fri, 07 Dec 2012 09:59:46 GMTdan-572483http://www.sqlservercentral.com/Forums/Topic1392541-392-1.aspx[quote][b]komal145 (12/7/2012)[/b][hr]I know , it's kind of DBA questions and they are excepting the Developer to answer it and I am a Newbie to SQL server ,and never faced such situations in realtime enviornment.[/quote]Did you tell them that you're new to SQL and are a developer? Or does your CV claim experience that you don't have?Fri, 07 Dec 2012 09:38:56 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic1392541-392-1.aspxI know , it's kind of DBA questions and they are excepting the Developer to answer it and I am a Newbie to SQL server ,and never faced such situations in realtime enviornment.Fri, 07 Dec 2012 09:27:45 GMTkomal145http://www.sqlservercentral.com/Forums/Topic1392541-392-1.aspx[quote][b]komal145 (12/4/2012)[/b][hr]Hi..I had an interview and had few questions:Can anyone please help me finding out answers for the below questions?1) Design table to track phone?2) how to troubleshoot high volume data?3)How to identify performance issues.4)Which statement is running slow, how to find it.5) How to Optimize stored procedures ?6)Suppose I hv 3 SP. SP A, SP B and SP C. SP A calls SP B and SP B calls SP C. If there is a problem with SP C then how we gonna use TRY and CATCH?Thanks,komal[/quote]These are questions that have a very broad scope and are part of the basic skill set required of the person holding the Role of "DBA". They don't have simple answers and they require actual experience doing all of those things. I apologize for the way this is going to sound, but if you can't answer these questions, then you're simply not ready to be a DBA.Use this as an opportunity to become ready to be a DBA. Buy a copy of the "Developer Edition" and use the questions above as a part of your study guide. Books Online and Google should become close friends. Once you dig into the complexity of how to do the things in the questions you've been asked, you'll understand why it would be difficult for someone on this forum to answer all of your questions to your satisfaction because it would involve the long process of actually teaching you how to be a good DBA.You should also Google for what a DBA actually is responsible for by searching for DBA job descriptions. Whether you pursue getting certified or not is up to you but the certification books identified by Microsoft are pretty good teaching tools so you might want to invest in a couple of those, as well. Google for Microsoft Certification SQL Server to find more information on those.Last, but not least, don't expect free love on these types of questions. Like I said, they form a part of the very backbone of becoming a DBA. Becoming a real DBA isn't easy. It's going to take a lot of work on your part. If you believe that you'll enjoy the job and the sometimes very long hours and taking "the heat" when something goes wrong, then it'll all be worthwhile. Just don't expect it to happen overnight because there's a lot to it. You should probably aim first at being an SQL Server Developer and get really good at T-SQL, indexes, and have a really good grasp on all of the idfferent types of objects.Wed, 05 Dec 2012 07:20:54 GMTJeff Modenhttp://www.sqlservercentral.com/Forums/Topic1392541-392-1.aspx[quote][b]Alan.B (12/5/2012)[/b][hr][quote][b]Your Name Here (12/5/2012)[/b][hr]Sorry to be a bit off-topic but this thread flashed me back to an interview I had years ago. The 'technical' questions about troubleshooting were surprisingly specific and detailed. After more than a few - all along the same basic problem - I stopped the interview and asked why all the questions centered around one type of issue. After a few moments of dead air, they finally admitted they had a problem with one of their production databases and was looking for ways to fix it.I left shortly after.[/quote]That is a great story. Hilarious! Its a shame that they wasted your time but you got a good story out of it.[/quote]I can hear the IT manager yelling down the hall, "Hey Bob, we have another issue on the production database, schedule some more interviews!"Wed, 05 Dec 2012 07:10:08 GMTtoddasdhttp://www.sqlservercentral.com/Forums/Topic1392541-392-1.aspx[quote][b]Your Name Here (12/5/2012)[/b][hr]Sorry to be a bit off-topic but this thread flashed me back to an interview I had years ago. The 'technical' questions about troubleshooting were surprisingly specific and detailed. After more than a few - all along the same basic problem - I stopped the interview and asked why all the questions centered around one type of issue. After a few moments of dead air, they finally admitted they had a problem with one of their production databases and was looking for ways to fix it.I left shortly after.[/quote]That is a great story. Hilarious! Its a shame that they wasted your time but you got a good story out of it.Wed, 05 Dec 2012 06:54:57 GMTAlan.Bhttp://www.sqlservercentral.com/Forums/Topic1392541-392-1.aspx[quote][b]komal145 (12/4/2012)[/b][hr]Hi..I had an interview and had few questions:Can anyone please help me finding out answers for the below questions?1) Design table to track phone?[/quote]It totally deppends on the business requirements means what data they want to store.[quote]2) how to troubleshoot high volume data?3)How to identify performance issues.4)Which statement is running slow, how to find it.5) How to Optimize stored procedures ?[/quote]For above question as Sean suggested these are topic for discussion and you can find out lot of articles on little google search.[quote]6)Suppose I hv 3 SP. SP A, SP B and SP C. SP A calls SP B and SP B calls SP C. If there is a problem with SP C then how we gonna use TRY and CATCH?Thanks,komal[/quote]May be I did not understand the question because what does mean how to use TRY and CATCH or what is the relation of having child procs with TRY-CATCH.Wed, 05 Dec 2012 06:44:09 GMTrhythm.varshneyhttp://www.sqlservercentral.com/Forums/Topic1392541-392-1.aspxSorry to be a bit off-topic but this thread flashed me back to an interview I had years ago. The 'technical' questions about troubleshooting were surprisingly specific and detailed. After more than a few - all along the same basic problem - I stopped the interview and asked why all the questions centered around one type of issue. After a few moments of dead air, they finally admitted they had a problem with one of their production databases and was looking for ways to fix it.I left shortly after.Wed, 05 Dec 2012 06:26:28 GMTYour Name Herehttp://www.sqlservercentral.com/Forums/Topic1392541-392-1.aspx[quote][b]komal145 (12/4/2012)[/b][hr]Sorry the questions is like this: Design a table, how to track phone call.[/quote]I stand by my comment that this entirely too vague to provide an answer. What does that mean? Do you want to know from the perspective of a cell phone provider? billing? etc. Track what? Do you need to know which towers the calls is handled from? Do you need to know the total time spent on a given providers network? Or do you want to track a phone call from the perspective of one end of the phone call. Maybe from the perspective of a amusement park you want to track the phone call so you can monitor traffic flow of pedestrians. Maybe you just want to know the number called and the call duration. See my point?Tue, 04 Dec 2012 10:17:37 GMTSean Langehttp://www.sqlservercentral.com/Forums/Topic1392541-392-1.aspxSorry the questions is like this: Design a table, how to track phone call.Tue, 04 Dec 2012 09:59:07 GMTkomal145http://www.sqlservercentral.com/Forums/Topic1392541-392-1.aspxdesign table to track phone? :hehe::crazy:what kind of question is that?Tue, 04 Dec 2012 09:26:10 GMTravulas2007http://www.sqlservercentral.com/Forums/Topic1392541-392-1.aspxQuestions 1 and 5 do not have enough details to provide an answer. I would be asking for a lot of clarity about what those mean. 2, 3 and 4 are not questions that have an answer. They are intended to start a discussion about how to do those things. This is more of a role playing technique than anything else. If you can discuss a number of things you would do that is what they are after. Of all of those I find the "how do you optimize a procedure" to be the most outlandish of them all. The interviewer wants to see if you know that the question is loaded. There is not a formula for this. It is more of an art than a science. Optimizing queries takes the culmination of all your knowledge in one location. Even worse is that you might optimize a query today and in a year you go back and realize a number of improvements you could make because you have learned new things.Tue, 04 Dec 2012 08:39:23 GMTSean Langehttp://www.sqlservercentral.com/Forums/Topic1392541-392-1.aspxHi..I had an interview and had few questions:Can anyone please help me finding out answers for the below questions?1) Design table to track phone?2) how to troubleshoot high volume data?3)How to identify performance issues.4)Which statement is running slow, how to find it.5) How to Optimize stored procedures ?6)Suppose I hv 3 SP. SP A, SP B and SP C. SP A calls SP B and SP B calls SP C. If there is a problem with SP C then how we gonna use TRY and CATCH?Thanks,komalTue, 04 Dec 2012 08:32:03 GMTkomal145