Multi SIMS Database on Multi Domains

[nikoxley]

What I'm trying to achieve, is a connection to sims from a users laptop that visits both sites

 

We have a Secondary school on Domain A with a Sims server of Servername\SIMS2012

 

We have a Primary School on Domain B with a sims server of ServernameB\SIMS2012

 

These 2 domains are completely seperate

 

Both use the same database name SIMS

 

Both sites use Network drive M: ( Is it possible to have the SIMS drive mapped for two different drive letters one for each school)

 

I have tried using a connect.ini that allows me to select the site

 

[sIMSConnection]ServerName=SITE1\SIMS2012DatabaseName=simsServerType=SIMSSQLCommandTimeout=1000000DatabaseMode=OnLine[simsDatabases]FriendlyName0=SITE1Server0=SITE1\SIMS2012databasename0=simsDatabaseMode0=OnlineFriendlyName1=SITE2Server1=SITE2\SIMS2012,50290databasename1=simsDatabaseMode1=Online[sIMSOffline]PreviousRedirect=PreviousServerName=SITE1\SIMS2012PreviousDatabaseName=simsPreviousDatabaseMode=OnLine

 

Site one connects fine but when on site 2 keep getting login reason 0

[Zammo]

Would a script that changes the connect.ini be a possible solution? Can always be packaged as an exe.

 

You could utilise proxyswitcher to do this plus other actions as well:

 

Proxy Switcher

[3s-gtech]

The network drive shouldn't matter if the connect.ini doesn't redirect to it (ours does so we only have to change one file to shift database connection). I haven't tried using the two sites in one connect.ini before - we did it with a script that switched the mapped drive, and subsequently switched the redirected connect.ini, which worked fine. Yours is more slick, but all I can say is double check the syntax (maybe post it here again in a clearer form too).

[Jonah]

We have a similar set up at two of the schools in our MAT, where some staff are shared across two sites so need access to both SIMS instances regardless of where they are.

 

We had trouble with the single connect.ini with multiple DB entries, so the best solution we found was to copy separate connect.ini files to all machines in a folder for each school on the C:\ drive, then use separate shortcuts for the two different schools (as you can specify the connect.ini location using a parameter).

 

So at each school we have a C:\SIMSConnectFiles\ folder on each machine, with a folder for SchoolA with their connect.ini in, and a folder for SchoolB with their connect.ini in.

 

The SIMS shortcuts are then:

SchoolA - "C:\Program Files (x86)\SIMS\SIMS .net\Pulsar.exe" /CONNECT:"C:\SIMSConnectFiles\SchoolA"

SchoolB - "C:\Program Files (x86)\SIMS\SIMS .net\Pulsar.exe" /CONNECT:"C:\SIMSConnectFiles\SchoolB"

 

This has been a flawless solution for us so far (aside from the odd member of staff using the wrong shortcut then telling us SIMS is down as their password doesn't work!)

[djm968]

So at each school we have a C:\SIMSConnectFiles\ folder on each machine, with a folder for SchoolA with their connect.ini in, and a folder for SchoolB with their connect.ini in.

 

This is exactly how I used to do it.

Edited November 1, 2018 by djm968

[Esteban_Child_of_the_Sun]

Why do you have ",50290" after server 1's SQL instance?

[cullingsh]

We have a connect.ini with about 10 schools in. We found that for it to work properly, the user needed to have modify permissions to the sims.net folder.

[matt40k]

Why do you have ",50290" after server 1's SQL instance?

SQL on a different port and no SQL Browser service... i guess