Multiple Instances in .Net environment

Is there anybody out there who runs multiple instances with their .Net environment? We are wanting to run legacy and test instances in our environment but have never setup multiple instances on a single server. Looking for information on how to do that.

Find more posts tagged with

VISUAL - Enterprise General Discussions

Comments

unknown

I can tell you, i tried to run 2 instances on the same SQL Server and performance suffered greatly.

It's all about the performance of the SQL server. We run test databases on a test server. We have as many as 6 copies of our Visual database running at one time on the same server. Our production server just runs production databases, but it's also massive with 24 SSD drives and 100GB of RAM, and all the SQL split up on different spindles for logs, data, and tempdb.

unknown

So what do you do now? Do you run a test environment and if so, how long does it take you to refresh the .Net test environment with your production database? This is one of our biggest issues. Manufacturing db is easy to refresh but .Net seems to take hours.

We only use .net with IQM that we got this year, so I have not spent much time with it.

So your saying the restore of the .net SQL database is taking hours? That seems odd if it's just a SQL database.

0811181026417683.xls

unknown

what Version of IQM are you using?

unknown

I must of misread at first what you were asking... but we do run multiple DB's on 1 SQL server, we do not run multiple instances, as running that is what causes performances to suffer. it was trying to do IQM and visual on the same sql server.

we run our normal DB, and when i want to connect to the test Db, i type the test DB name in, on the login screen. Also, make sure you have it listed on your SQL.ini folder, otherwise it wont work

unknown

I don't want to make it sound like the system is taking that long to restore the db. What I mean is that in order to restore, the person doing this (I am the Controller and don't do it myself) has to rebuild quite a bit of information on SQL and then rebuild security roles, etc. in order to restore it. The time it takes to do that every time makes it not worth having a .Net test environment. Obviously though that means when we have issues it is hard to test solutions. What we really want is a test environment that is a direct refresh from the production database and then a sandbox environment where we can test upgrades and patches prior to applying them to the production database.

Copyright © 2025 Infor. All rights reserved.