can any one give me advice on installing navision 3.7 on SQL server with clustering? should there be 2 clients? if so how are logins managed.
Do you know what a cluster under MSSQL is? You need only one installation and one login.
quote:
Originally posted by JHC
can any one give me advice on installing navision 3.7 on SQL server with clustering? should there be 2 clients? if so how are logins managed.
sorry,Let me clarify, i mean Microsoft cluster service MSCS being used on windows 2003 server. with Navision 3.7client and SQl server.
It works with the following config: Cluster Windows 2003 Enterprise Server Cluster SQL Server 2000 Enterprise Edition For your users, they will only see 1 server, 1 Database. And if you intend to use the Integrated Login on Navision, you shouldn’t have to worry about how many login… But let me be clear with you on one thing… SQL Server Cluster currently only support “Fail Over”, there is no “Load-Balancing”. So, even if you “Load-Balanced” your Windows 2003 Cluster, you will not see any performance gain. To get some major speed gain under SQL Navision, you have 2 choices: 1) Solid-state disk array, we are talking major cost here. Last I check, it is in the 6 figure range. But it does cut a 8 hours process down to 30 min. 2) Disk array with a lot of drives, and I mean a lot of drives (say, 32 or more).
Thanks a lot.we r using disk array with lot of drives… ,i have one hiccup here! the server is located in differnt building … as a secondary option we are planning to use microsoft terminal server. so i ahve to install client in both the nodes,at failover ,eventhou the terminal service is ‘shifted across’,user has to login again! is there any way to avoid this. can we cache the user id and password in any way and use it again. this was demonstated in SAP r3 under similar conditions. I understand the brwoser played a important role and architecture is differnt. but any chance,either using OCX and stroing it out in an external file. thanks in advance