Having many companies in one database gives problems in terms of: 1. There is no problem with having many companies in normal day-to-day use. (From version 3.10 you can have separate licenses per database). You can create as many databases as you like on the server - but doing this in order to have separate companies may cause problems with your application processes, since each company will be essentially hidden when working in a particular database.
NOVELL FILR NAMED SQL INSTANCE LICENSE
Gedas, your license file applies to an entire SQL Server. of Companies is a problem, have you tried speaking to Navision?
NOVELL FILR NAMED SQL INSTANCE CODE
SQL Server works differently with keys and you may find turning off certain keys that aren’t used or restructuring code to use different (better equiped) keys, improve performance. The Navision coding has been in place for near on 8 years and has structuring problems and needs to be investigated for optimization purposes. It’s not even a solution to throw more hardware at your problem (ie: more disks, RAM and CPU’s). Sure, with a small database and small number of users, you could probably get away with it. But moving to the SQL option is not just a straight forward backup and restore. I have heard of many SQL option installations from people who say the system is running slowly. I have to agree with Robert’s remarks (as stated above).
Gedas, Quote Have you moved over with regard to looking at problem areas with your SQL solution, identifying problem queries, looking at keys and application code that is not suitable for SQL - or just with your fingers crossed? Because the latter will not work. I think our about 14 000 tables are more then enough when i am scrolling trough them to do index optimalizations or other operations where i need to work on single tables. Each company will have over 1000 tables, and just navigating trough your list of tables from within SQL serveres Enterprise mananger could be a challange. I am not afraid that it would work, but preformance and administration of a database with the numbers of tables and indexes you will have could be a problem. I am saying this without knowing the size of each company, but i think that no matter how small they are it would not be a good idea to put all theese comapnaies in one database. With the number of companies you are talking about i think i would seriously consider to split them on several serveres so that one servere dosn’t have to carry all this load. Also remember to put your tempdb on a very fast disks. Many small disks are better then few big ones. Spread your databases over as many disks as possible. But we think that our main bottleneck at the moment is the preformance of our storage systems, Navision is very I/O intensive and with the number of companies and user your planing on running you need to plan this very well and make sure you get the fastes storage your client can afford. Our server is equipt with 8 processors and 6 GB of memory and we could still wish we had more power in certain situations.
We are running 100 users on SQL sever, we have 8 companies in our database and the database is now at 194 GB.
One thing you also have to take into consideration is the excpected size of you database, and don’t forget or underestimate the need for a proper and fast storage solution. I think the recommandations you got are kind of weak.
0 kommentar(er)
