iStock-648182720.jpg

At the recent BizONE Conference in Anaheim, I had the opportunity to catch up with Rob Burke from McCroskey Mattress Company, a long time user of SAP Business One and we got to chatting about performance tuning SAP Business One on SQL Server and what were the basic things that should be done to keep your SQL Server running at its optimum.

 

 

In prior years you would need to set up a number of manual SQL Maintenance jobs to re index and compress the databases as a starting point, not to mention running the regular backups of the data.

 

 

The good news is that now, with the Remote Support Platform you can set up those tasks based on downloaded tasks that come in from SAP as well as a number of other repair and system validation checks.

 

 

Theres also a number of other things to look at with the setup of your SQL Server deployment that I wrote about a few (actually more than a few) years back so i thought I would post them here as Rob dropped me an email following up on our conversation yesterday.

 

 

 

So here's the links for you Rob and for anyone else that may find them useful...as well as some other blogs and contributions from others in the general B1 community

 

 

Rob also was asking about the impact of increasing the number of cores on their SQL Server and whether or not this would force them to generate a new license key.

This one is open to conjecture - my understanding is that if all you are doing is allocating more cores to SQL Server (from the SQL Management Console) then it wont impact it - the disabling of the license key when there are major changes was introduced to prevent moving from one machine to another so this shouldn't really have an impact.

 

But if it does, of course, you can generate a new license key immediately as long as you have an S number and access to the rights to generate a key, which your partner should have given you.

 

Here's a short video that shows you how to do it