Mark Aufflick said: > I have seen some large Sybase databases go down quite spectacularly. Any details on how or why? One common cause for downtime is filling up the log space and locking up the DB, not knowing how to fix it. But they should have read the manual!
> Most of the web world runs on MySQL and does ok - just like CDBaby who You can't possibly liken Sybase to MySQL! > with Sybase because you end up needing more lines of code. That is a > purely gut feel however. I don't see why, what do you think Oracle offers that Sybase doesn't and gives it an advantage? 99% of applications I see are nothing more than straight SQL jobs. And even when stored procs are involved, I find T-SQL a much nicer and language than PL/SQL and uses less code to achieve the same thing. > Further, my experience with large-ish (some millions of rows and many > tables) databases is that Postgres scales to that size easily and > needs even less support than Sybase. The support people probably need > to be smarter though, especially if you use replication. Definitely, Postgres is my first choice. It took me a while to get back to it after being severely burned by 6.5, but now it seems great. But if a client wants a commercial DB, I will always push for Sybase. Luckily, most clients already have big Sybase production enviroments, so using that is usually a given. "Enterprise" features like replication is one of the things that lets it down. While miles ahead of "the other free database", backup isn't great either. The version 8 option of "stop checkpoints, copy data files" and the automatic archiving of log files is nice, but they need to go one more step to the equivalent of Sybase's "dump database" and "dump tran" commands. Cheers, Bas. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
