SQL Injection Pocket Reference

There is significant portion of customers which are still using MyISAM when they come to us, so one of the big questions is when it is feasible to move to Innodb and when staying on MyISAM is preferred ?

I generally prefer to see Innodb as the main storage engine because it makes life much simpler in the end for most users – you do not get to deal with recovering tables on the crash or partially executed statements. Table locks is no more problem, hot backups are easy, though there are some important things which we have to consider on case by case basics before recommending the move.
 

Is MyISAM used as default or as a choice ? This is the most important question to ask upfront. Sometimes MyISAM is there just because it is default, in other cases this is deliberate choice with system being optimized to deal with MyISAM limits, for example there is a dedicated slave available for all long reporting queries. In case MyISAM was chosen not just happened to be it is important to build the good argument to suggest Innodb.

Application Readiness Application should be ready to work with Innodb, for example be ready to deal with deadlocks which can happen with Innodb even if you do not use transactions, but which are not existent with MyISAM. QA has to be performed as part of the move.

Performance Innodb has a lot to offer in terms of performance – Performance benefits and drawbacks. On the benefits side we usually see clustering by primary key, caching data, higher concurrency, background flushes while on the drawbacks side we see significantly large table size (especially if data size is close to memory size), generally slower writes, slower blob handling, concurrency issues, problems dealing with very large number of tables, slow data load and ALTER TABLE and others. Another big one is COUNT(*) without where clause which is often the show stopper for them move until it is worked around.

Operations What is good for MyISAM kills Innodb, such as copying binary tables between the servers. It is important the team understands Innodb and knows how to handle it, or be able to learn it. It is also important to adjust processes as required to work with Innodb. For example binary copy of one of the databases from the Slave to the dev envinronment works great for MyISAM but does not work with Innodb. Backup tools like “mysqlhotcopy” does not work etc. Note Performance also affects Operations aspects a lot – for example using mysqldump as a backup may well work for MyISAM but will start taking way too much time to do restore for Innodb. On large scale installations mysqldump does not work anyway but it may still work for you when you’re running MyISAM but instantly break upon upgrading to Innodb.

Features The MyISAM features which forbid moving to Innodb are typically Full Text Search and RTREE indexes/GIS with Full Text being much more common. There are workarounds for both of them, including dedicated MyISAM slave or shadow table but it is important to consider them.

How about Mixing Storage Engines ? Sure you can mix storage engines but I suggest you doing is wisely. It complicates operations tasks (backups, balancing, performance analyzes) as well as it exercises not so common paths in the MySQL server – in particular Optimizer may have harder time because costs between storage engines may not be well balanced or replication of mixed table types which is quite complicated.

I prefer to pick one storage engine (typically Innodb) and when use other tables when it really gives substantial gains. I would not switch table to MyISAM because it gives 5% performance improvement but I can perfectly use MyISAM (or Archive) for logging.

Innodb Needs Tuning As a final note about MyISAM to Innodb migration I should mention about Innodb tuning. Innodb needs tuning. Really. MyISAM for many applications can work well with defaults. I’ve seen hundreds of GB databases ran with MyISAM with default settings and it worked reasonably. Innodb needs resources and it will not work well with defaults a lot. Tuning MyISAM from defaults rarely gives more than 2-3 times gain while it can be as much as 10-50 times for Innodb tables in particular for write intensive workloads. Check here for details.

Note: As Few people questioned me, I indeed forgot to clarify the scope here – I’m mainly speaking about OLTP/ Traditional web applications. for Analytics things are a lot different.

reposted from http://www.mysqlperformanceblog.com/2009/01/12/should-you-move-from-myisam-to-innodb/

There are strong indications that Google Plus will become a powerful marketing tool for business, but there’s a problem: the service is not yet allowing businesses to create profiles. So what to do? Should this stop you from using it to build your brand and get more customers? We say no. Here are five ways to play.

1. Be the front man.

Google won’t let your business have a profile, but you certainly can create an individual profile and post business-related material to your circles. (More about circles later.) In some ways, that’s even making a virtue out of Google’s restriction, by forcing you into being the front man or woman for your company.

2. Invite your existing followers.

In the very earliest days, invitations to Google Plus were about as common as gold tickets in Willie Wonka bars. Things have loosened up, and users can now get others through the door pretty freely. Send invitations to your best and most electronically engaged customers first. Import your Twitter, Facebook, and LinkedIn followers, and maybe even look at your customer/CRM list.

Side note: You may find it difficult to import your Facebook friends or fans. Facebook recognizes the threat posed by Google Plus and has blocked several services that do this.

3. Use circles to segment your contacts.

The organizational metaphor of G+ is that of “circles.” You assign your contacts to one or several circles of acquaintance or interest. The metaphor is literal in the user interface when you start out: you drag people onto circles that you can create and name.

Here’s a key: you can create any number of circles you like and name them whatever you want. Here’s another key: one person can be in any number of circles. And the last key: you can send individual posts to any circle or circles you want.

If you’re an accounting firm, you can create circles for each of your professional staff, and assign contacts as appropriate. You can also create circles for each function (bookkeeping, taxes, legal issues, for instance) and assign the same contacts in the appropriate circles. It would be nice if you could send posts to subsets of circles — all of Mary’s clients who have tax issues – but that will have to wait. For the time being, you can send posts to Mary’s clients, or clients who have tax issues, but not the intersection of those circles. But you can also send a post to Mary’s clients, Jack’s clients, and William’s clients with a single click.

Use the circle feature to segment your contacts.

4. Mind the +1 button for SEO.

In Facebook, it’s “Like.” In G+, it’s the +1 button. And, as with Facebook, the +1 is available to put on your own pages outside the confines of the social network.

But here’s the thing. Facebook tried, with great success, to keep search engines at bay. With Google Plus, search is the whole enchilada. It’s likely that Google will use the +1 button – on and off Google Plus – as another means to measure the authority of pages, posts, and people. So keep watching tounderstand how and whether this will impact your search engine rankings and SEO efforts. And if you’re bold enough to add a +1 button to your website, here are some instructions.

5. Keep monitoring the social media landscape.

Google Plus is brand spanking new. As with any startup, Google is pretty much building the road as people are driving on it, so the rules of the road are a little, shall we say, fluid. The G+ you’re engaging on today will be different from the one you’ll engage on next month, let alone next year.

The same is true for the overall social media landscape. Here is one interesting take on how Google Plus will impact competition between services that are already part of your marketing mix. It will be interesting to see how it plays out, but we’re betting that you’ll want your business on Google Plus.

reposted from -  http://blog.bestvendor.com/2011/07/should-you-be-marketing-on-google-plus/

It happens to most of us : you’ve got invited to some event. Mostly you don’t know who the f*ck is that guy , what’s the hell is going to happen & etc. 

Dear facebook engineers : If event is local , and it is thousands miles from me ( it’s 17 hours flight from Tel-Aviv to California ), please don’t send me invitations. I’m happy that some dude is throwing a party at his home, i’m happy that his start-up got 50k users. But I really won’t attend it. Even if he is going to pay for the ticket – I hate flying, yeah..

I’m really f*cking interested in tech meetings & parties near by.

Did you got my message right ?

If no, contact me , it’s easy , @themoah

Apple , the creators of Mac OS X , i hate you ! Why ? I switched to mac from linux , because i wanted “full unix power” with awesome GUI. Really. I need the httrack app. Why the hell should i download Xcode & lots of other stuff manually ? Why not to do with one line ? 

Google , creators of Gmail & Google apps , i hate you ! Why ? Why the hell do we pay 50$ per account with all very important e-mails don’t reach my email ? Or got to spam ? I’ll switch to rackspace e-mail service. Or anything else. Really. Hate you. ( Yeah , google reader is very needed thing. Don’t hide it. Don’t be idiot )

according to last news - Israel is way too safer place , than Moscow ( Russian Federation ) http://ow.ly/3J5ZU