Each location will have its own primary database. I want to be able to read/write from all locations and have all the servers clustered together so that if something fails, there won't be any problems.
Any "in production" solutions?
What would anybody recommend if I needed to have access to an MSSQL server from multiple locations and it needed to be edited on the fly. I know there is a replication feature embedded into MSSQL but am not sure if that would be the right choice? And if it is, What topology is commonly used?
It doesn't show any errors. Thats why I'm asking. It does its normal post and then it comes up F1 to continue and then F10 to go into the partition utility which is non-existant.
I want to make an Mdaemon server a store and forward. If my main mail server goes down, this is second in line so I want to have it recieve all the messages and store them. Then when the the main server comes back online, I want it to send all the stored email back on to the main server.
How can...
How do I get the server to stop bringing up the F1 dialog during startup. I have used the SmartStart CD and haven't found the option to change that will get that dialog off.
Thanks,
Christian Jensen
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.