Re: Witango-Talk: Witango 5.01.065 vs. 5.5.009 - PrimeBase vs. MS SQL

Fri, 17 Jun 2005 19:32:56 -0700

They may have, but I didn't know about it, and only in 55 docs were the big warnings about it, which I payed attention to.

I was not surprised by difference, and was hopeful. However, I was VERY surprised to see MS SQL instability with 5.01.065 under these conditions, and still with 55.

Most of my clients, I host in my own datacenter, and primebase is used. I do not host on your scale, I would consider myself a boutique. And I do not allow anyone other than BigHead developers to alter wtiango code if I host, so I can maintain application integrity for all custs. As you know, one malformed SQL statement, can bring down a rack.

But I have some other large clients, where my apps are deployed in there datacenters, and they are on MS SQL. For the most part the MS SQL witango apps have not crashed, so I have hammed primebase, and they have responded EXTREMELY helpfully. In the past, there were definite bugs in PrimeBase ODBC, so that is why I went there first. I now feel that primebase is more than up to snuff, and the rest of the issues were with Witango 065.

The reason Witango/PB was going down occasionally, and not Witango/MS, must just be traffic and load. Witango/PB is serving 10s of thousands of queries a minute, and just the one major site is averaging 4 million page views a month. And most of those pages contain 25-50 thumbnails that are blobs generated by witango/pb. Just one user hitting a eventpix event, may open 20 connections from zero, to view the 25 thumbs that just got requested instantly.

I would also like to make a plug for primebase, and understand, I pay a licence fee like anyone else, I am not on the payroll or anything. Not only have I proven to myself that the ODBC system from witango is more stable, but there are several other reasons why I use it.

1. The server is ROCK solid. We host millions of images tons of images (hows that for specific) and it doesn't burp. EVER. The only issue has been the PB ODBC system, but I think we have made sure that is up to speed.

2. PB has a unique way of storing blobs, that makes it extremely useful when managing large dbs with binary data.

3. PB runs on any server platform, and any platform witango can run on.

4. PB has an SDK for using this same engine as a desktop database, like MSDE, only on any platform, and I have been using it for years, it is SOLID and fast.

5. They listen to their customers and respond quickly. When I told primebase I was still dealing with some of these issues, and that I was being pressured to switch to MS SQL, they offered to fly an engineer to my office to work on it together. This is the number one reason I will stay with PB as long as possible. The relationship with them and speed to which they react, has been amazing.

Anyway, I am very thankful for their help, and the help of witango ( with ent ) to get this done, so I could provide stability to my customers.

If you decide to purchase from PB, drop my name, it will help to make sure they respond even faster to my bug issues, and make it a "TUNED" partner with Witango.


Maybe primebase could offer a competitive upgrade sale or something for witango users. (I am bcc'ing primebase, who knows)

-- 

Robert Garcia
President - BigHead Technology
VP Application Development - eventpix.com
13653 West Park Dr
Magalia, Ca 95954
ph: 530.645.4040 x222 fax: 530.645.4040

On Jun 17, 2005, at 1:23 PM, Robert Shubert wrote:

I could’ve sworn that Witango went to ODBC v3 around 5.0.1.058. And I’m not surprised that there is a difference here, since 5.5 has a largely reworked data source management system. Your testing is helpful, and I thank you for sharing your findings.

 

Robert

________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf



________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf

Reply via email to