we have a company in my town: second quadrant. the provide professional postgresql support worldwide and they pronunce it "postgres". omitting the final "ql"
That's the official pronunciation and it was originally spelled that way. The PostgreSQL spelling was added when it went open source.
Are the two SQL servers sitting side by side? If not, shared storage and low latency for it's use would be super expensive.
Though I do wonder how their DR plan works if there isn't a cluster for the DB, what purpose does the second server serve? Warm spare?
Yes the servers are side by side, basically just sits there, and when a new site is created on SP side, run the script which mirrors the new DB created on server 1 to server 2. Eventually they were planning to introduce the witness server once our testing is complete and then enable auto failover. The downside here is that someone need to manually run the script for db mirroring of new databases
So the big thing here is that the databases are not mirrored, just the framework (schema) is at creation time. Very different from mirroring or clustering at that aspect level.
Yes, we've told them this won't work and asked them to look at a clustered setup. Since the licenses are already in place and is SQL standard no option for Always-On. I want to know what would be the drawbacks for the clustered setup, as for sure there are some more advantages on Always-ON compared to the clustered setup.
Won't work... for what? What's the end goal?
Won't work: Current stage its 2 separate DB servers and mirroring needs to be done by executing a script whenever there is a new db is created by SP.
End Goal: A fully automated failover setup giving high availability for the SharePoint solution
What they are doing is unrelated to their end goal. How does mirroring database creation help with failover. There isn't even a first step in preparing for a failover here. What is going on is totally something different.
Holy crap, yeah, that's not useful at all. No wonder they do not publish the prices anywhere. The old rule of thumb applies: if the price isn't public, the price isn't good.
I'm a fan of Brent Ozar http://www.brentozar.com/blog/ though my knowledge of SQL Server is very limited. He sounds like he knows what he's talking about but I wouldn't know if he does or not. I haven't paid for any of their training videos, but I've watched a few of the free ones.
If I understand correctly, that code snippet is only for a validation that will be run against the Phone1 field. Are you just trying to throw up a validation error on a web page or within an application if a proper phone number is not entered in the PHONE1 field?
He wants to extract out the first 10 digits of the PHONE1 field and present them to the application / page as the phone number so that the native regional formatting of 10 digit TN handles it correctly.
