NAV on SQL Server - Maintenance and Setup Essentials

DenSter

At Convergence 2012 in Houston I'll be part of a session about best practices for NAV database setup and maintenance on SQL Server. In preparation for this session I've created a couple of videos:

Essential Maintenance: http://www.youtube.com/watch?v=0KbZkKdyZps
Setup Essentials: http://www.youtube.com/watch?v=pOIjde-xpz4

Marije_Brummel

Have fun!

davmac1

I will put your session on my list.
See you there. :thumbsup:

Alex_Chow

What software did you use to record the session?

DenSter

Camtasia Studio. The one with the bad audio was because it was set to pick up the system mic instead of my headset.

davmac1

Just watched both of your videos and I see you already answered the question I had - what did you use.

When it comes to basics, I like to recommend standard security and Case Insensitive (easier for external sql queries, and more standard with non-NAV SQL Server).
How do you feel about this?

Look forward to more of your videos.

kine

E.g. Case-Insensitive is basics for Czech databases, because else NAV have problem with searching for specific texts including character "ch" (one char in Czech alphabet, two chars in NAV, case-insensitiveness helps NAV to search correctly when you enable the "Match Case" option).

David_Singleton

davmac1 wrote:

When it comes to basics, I like to recommend standard security and Case Insensitive (easier for external sql queries, and more standard with non-NAV SQL Server).
How do you feel about this?

Yes I agree those need to be there, as well as at least touching on Recovery modes.

ajhvdb

Thank you for the time making this. :thumbsup: Now it's easier to explain to others.

DenSter

Thanks for the compliments guys

My intention with these two videos was to focus solely on SQL Server, and I wasn't planning to address any settings in the NAV client at all, opening that kind of happened in the spur of the moment. They both come in at around 15 minutes and I thought that was enough as it is anyway

As far as the collation I don't really care about that, I've never had any issues with the default one, since the databases that I work with are all in the US and the default collation is fine for those. For sure if you are on an international database you have to be aware about the implications of the collation, but since I don't work with that I don't feel that I am qualified to say anything about it.

The security model should definitely be set to standard. I'll put together another video to go into more detail about database settings in the NAV client.

Resender

Txn, wass looking for something like this a few weeks ago, when I had to look into how to migrate from Native to SQL and what would be needed to set it up & maintain it.

Off course, the moment I wanted to put in my findings, the manager of the IT department decided we're going to keep using native.

Alex_Chow

The video is some serious MVP stuff. :thumbsup:

This is what MVPs are about, giving useful information to the community without asking anything in return. =D>