Exam 70–431: TS: Microsoft SQL Server 2005 - Implementation

Tomas

As some people are already thinking in SQL, I've decided I might join them.

I've registered for the 70-431 exam: Microsoft SQL Server 2005 - Implementation and Maintenance, as this is the first step for SQL certifications. Therefore, I wanted to ask, any suggestions, ideas on what's the best way to prepare for it?

Basically, as I understand you need to practise a lot, however while working with NAV my practise with SQL isn't huge (backups/restores/some sql queries). Therefore, where should I start?

Thanks.

Tomas

I've found interesting topic - table partitioning. It's possible in SQL to divide your enormous tables, however... would navision like it? Have anyone of you seen such divided tables while working with NAV?

DenSter

You can get books that will prepare you for most Microsoft exams (of course that doesn't apply to Dynamics :-k). There is definately a set of books for the SQL Server exams by Microsoft Press, and there are plenty of alternatives. Keep your exam number handy, go to the bookstore and prowse the computer section. You can also browse around here.

Good luck on the exam

Kenneth_Verburg

Hi Tomas,

I did the exam last week, the book I used for it is the Microsoft Press book "MCTS Self-paced Training Kit (Exam 70-431): Microsoft SQL Server 2005 Implementation and Maintenance". Since I passed the exam I think the book is a good preperation for the exam.

Tomas

Thanks Guys.

Anyway, it's about time I would start fighting my "to-read" SQL book lists ;-) Just the problem is, that when it comes to navision, same things usually are done differently for navision and there are no books regarding that.

msi

Try SQL Exercises.

geschwint

Real life SQL Server experience will result in a much better understanding with regards to the internals of SQL Server which will further help when solving issues without the need to search the web.

Partitioned Tables can be used with Navision but its a 100% manual setup and will cause the redesign of a table to stop working properly in some cases (but coding in the table works, so does adding columns). So, it is not all that practical. Also, rules in SQL server must be defined beforehand that controls what data goes to which partition.

I'll dig up my lab where I did the above and post it in tricks & tips..

One big advantage would be if used on Ledger tables where historical data then could be saved on a slow-but-big generic storage and the current year (for example), could be sitting on the super fast RAID 10 system.