Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
vikashsql
Starting Member
6 Posts |
Posted - 2008-06-06 : 01:47:31
|
Hi AllI've been working in production support for last one and half year . And most of the work i do is making some changes in Stored procedures as per change in requirement or data fix if there is any production issue.I've worked on SQL 2000 and 2005 . I've worked on SSIS also . I can say, i have major experience in these two . Other than that i've little knowledge in Biz-talk and .Net but never worked in any project .My question is what should be my path from here ....i'm intrested in datawarehousing but not much hands on expereince . And was also thinking about DBA . Please suggest me what should i pursue , certifications and other things which i should learn as i feel i'm not learning much on the job here . And i may not be readily employable if i think of switching job. If it helps....my long term goal is to become a DB consultant .Please note that i'm based in India .Waiting for replies from all expereinced ppl.Edit: Moderataors ..plz let me know if i've posted in the wrong thread. |
|
AndrewMurphy
Master Smack Fu Yak Hacker
2916 Posts |
Posted - 2008-06-06 : 10:21:16
|
build a general log of your weekly activities...typs of actions actioned.try to understand what changes you're executing, why and how they improve the current position.learn the TSQL language contructs...it doesn't have to be them all.download the MSDE kit (or 2005 equivalent) for free home use.observe the questions and answers posted here.hands-on experience is a must regardless of the career direction. books and college only get you 40-60% of the way.getting into a production DBA role (backups, restores, configuration, BRP, etc) is one route - usually involves a lot of out of hours work (downtime usually is nighttime/weekends in most industries)a development DBA concentrates on optimisation and database design...code improvement, code QA, etc, usually a day-time role but can be a lot of "pressure" coming close to deadlines.sql programming would may give you practical routes into dealing datawarehouses...there are different roles ... setting them up, filling them, running them efficiently, extracting the data and making it useful for others - it's too broad a brush to say I want to work with datawarehouses....some people will say excel is a datawarehouse |
|
|
|
|
|
|
|