Solved
Location for SQL Server - in a bind
When we were first sold EV, we were told the SQL databases were for config info only, so here at HQ, we loaded the SQL databases on our utility SQL server. Since then, we've learned that the SQL databases do much more than hold the config info. If I'm correct, they track every message in and out of the archive, where they're stored, etc. right? Anyway...
We're installing EV at our 3 remote offices, each it's own separate EV site. Unfortunately, we do not have the luxury of loading SQL on any of the existing servers and purchasing 3 new servers is a last resort. According to the documentation, the SQL databases can be loaded on the EV server for demo purposes, but has anyone had any luck/perfomance problems with doing this in production?
OR...
Can the remote sites use our SQL server here at HQ over the T1 lines? If we turn off auditing?
Environment:
E2K3 sp1
EV 6.0 SP2 on W2K3 sp1
Our remote offices have between 50 and 70 users each connect via T1 lines.
Total archive size for each office is anticipated to reach 500 GB in 2 years.
Servers are HP DL360 G4s (dual xeon 3.2ghz w/ 3 GB ram), EV data is stored on SAN (FC @ 2 gbps).
We're installing EV at our 3 remote offices, each it's own separate EV site. Unfortunately, we do not have the luxury of loading SQL on any of the existing servers and purchasing 3 new servers is a last resort. According to the documentation, the SQL databases can be loaded on the EV server for demo purposes, but has anyone had any luck/perfomance problems with doing this in production?
OR...
Can the remote sites use our SQL server here at HQ over the T1 lines? If we turn off auditing?
Environment:
E2K3 sp1
EV 6.0 SP2 on W2K3 sp1
Our remote offices have between 50 and 70 users each connect via T1 lines.
Total archive size for each office is anticipated to reach 500 GB in 2 years.
Servers are HP DL360 G4s (dual xeon 3.2ghz w/ 3 GB ram), EV data is stored on SAN (FC @ 2 gbps).
- If these are the specs for the EV servers in the remote sites:
Our remote offices have between 50 and 70 users each connect via T1 lines.
Total archive size for each office is anticipated to reach 500 GB in 2 years.
Servers are HP DL360 G4s (dual xeon 3.2ghz w/ 3 GB ram), EV data is stored on SAN (FC @ 2 gbps).
Then I do not think they will see that poor of performance for the number of users they are talking about. The big thing is to not let SQL still all the memory.
the biggest concern to me would be the SAN storing the data, if the link goes down the users will not be able to get to the data and archiving won't work. If the storage is going to be going over the network you might as well go w/ a centralized solution.
