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?
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.
is pronounced ree-bar and is a Modenism for R
First step towards the paradigm shift of writing Set Based code: Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
Although they tell us that they want it real bad, our primary goal is to ensure that we dont actually give it to them that way.
Although change is inevitable, change for the better is not.
Just because you can do something in PowerShell, doesnt mean you should. Helpful Links:
How to post code problemsHow to post performance problemsForum FAQs