Does your company use the form ID-10T is response to a users question?

Does your company use the form ID-10T is response to a users question?

• Yes!
• That is not nice!
• We would like to!
• No! 

EXPLANATION

ID-10-T error

ID-Ten-T error^[11] (also seen as ID10T and ID107) is a masked jab at the user: when ID-Ten-T is spelled out it becomes ID10T ("IDIOT"). It is also known as a "Ten-T error" or "ID:10T error". The User Friendly comic strip presented this usage in a cartoon on 11 February 1999.^[12]
In United States Navy and Army slang, the term has a similar meaning, though it's pronounced differently:

• The navy pronounces ID10T as "eye dee ten tango".^[13]
• The army instead uses the word 1D10T which it pronounces as "one delta ten tango".

 

Read More

Which is faster? Inserting 1 Million rows of data or Updating 1 Million rows of data?

Which is faster? Inserting 1 Million rows of data or Updating 1 Million rows of data?

• It depends
• Updating
• Inserting
• Google it! 

 

EXPLANATION

INSERT is always faster because UPDATE necessarily requires a scan(whether aided by indexes or not) to find the individual row(s) to alter. By contrast, the database engine already has the next locations in each table allocated and identified for INSERT actionsand maintains this information in the control files.
INSERT is also faster than DELETE and INSERT as a substitute for UPDATE for two reasons: not only is the database required to _find_the rows to DELETE, but it must maintain the UNDO for BOTH the DELETE and INSERT actions in the redo logs. A DELETE will take just as long as an UPDATE by itself. Adding the additional INSERT afterwards only further increases the time differential. 

SQL> --create table juva as select * from dba_objects
SQL> truncate table juva
Table truncated.
Elapsed: 00:00:01.09
SQL> insert into juva select * from dba_objects
71238 rows created.
Elapsed: 00:00:02.12
SQL> commit
Commit complete.
Elapsed: 00:00:00.17
SQL> update juva set object_type = 'unknown'
71238 rows updated.
Elapsed: 00:00:05.97
SQL> commit
Commit complete.
Elapsed: 00:00:00.20

 

Read More

Who is the most important user of a database?

Who is the most important user of a database?

• Payroll
• The Database Administrator
• Everyone
• The current user with a problem 

EXPLANATION

 Short answer, from a DBA's point of view - Each person who logs into the database. A DB system is there to provide data to the end user. If users can't get their data the database is useless. "Important", in this case, is an extremely subjective term.

Read More

What kind of service provider gets the same benefits from a composable system that a user does?

What kind of service provider gets the same benefits from a composable system that a user does?

• CaaS
• Cloud-based storage
• PaaS
• AaaS 

 

EXPLANATION

#1 Innovate Faster

First and foremost, using a PaaS to deploy and run your application enhances your agility.
The Web is accelerating the pace of innovation. To compete, you need to quickly transform new ideas into real applications and evolve those applications with agility in order to meet fast-changing business and technical requirements. Market opportunities exist very briefly. Your business needs to build, deploy, and iterate in days or weeks, not months or years.
Setting up platform-level software to run your application is time-consuming and complex. By simplifying, automating, and in many cases eliminating the steps associated with setting up the foundation for your application, you can get your application deployed much more quickly in the first place, and you can iterate, adapt, and extend it more rapidly over time.

It takes us 50% less time to deploy on Engine Yard Cloud because it’s so easy to configure servers. We can deploy with just a few clicks and add another instance with just one more click—and on top of it all, everything is pre-configured by Rails experts at Engine Yard who could write the book on best practices for rapid deployment.

---

Do-it-Yourself on EC2 Use Engine Yard PaaS	Use Engine Yard PaaS
Initialize Build app Set up EC2 account For each desired instance: a. Install/configure OS b. Install desired language version, runtime c. Install frameworks and other libraries/gems d. Install/configure application server e. Install/configure HTTP server f. Install/configure load balancer g. Install/configure other components (DB, cache) h. Debug integration of stack i. Install/configure application on stack Get instances working together	Initialize Build app Set up Engine Yard account Click several configuration choices Click “Boot”
Update Repeat items a-i above, per instance Get instances working together	Update Use Update Instances wizard
Scale Do a-i above for new instances Reconfigure application servers, load balancers, DB, etc. Ensure consistent stacks Get instances working together	Scale Use Add Instances wizard

---

 

#2 Focus Resources

Eliminating much of the overhead to deploy and manage applications doesn’t just mean you can do certain things faster. It means you don’t have to do certain things at all. Which means that you don’t even need to know how to do them. Which allows you to be even better at knowing how to do the things that differentiate your business, like building applications with innovative features and exceptional user experiences.
Let’s say you’re an entrepreneur with a great idea and some seed funding, or you’re an enterprise line-of-business manager with some spare budget you’d like to put on a special project. Do you want to spend your precious funding on some generalist developers who can code moderately well and also do system administration, or would you rather get top-notch coders who don’t necessarily have deployment expertise? Would you rather spend a dedicated headcount on an ops person or have an additional application developer?

By deploying on Engine Yard Cloud, we’ve saved at least 60% on engineering resources—this productivity boost translates directly to more features and faster time to market.
- Chris McNeilly, CTO, Motista

 

#3 Save Money

Focusing development resources and spending less headcount on unneeded expertise are both benefits that intuitively translate into reducing costs. But beyond these obvious things are even more ways that PaaS saves real money compared with doing it yourself on IaaS.
With PaaS you are tapping into a real economy of scale. Imagine the number of hours it would take to set up the core stack—the platform-level components—for your applications. Imagine the hours consumed on an ongoing basis to maintain the stack. Imagine the cost of those hours, and consider the incremental value from this work to your application. Now consider those same costs amortized across thousands of applications. There is very little differentiating value from doing this low-level work yourself, so clearly, buying platform from a provider is more efficient than building it yourself.

We estimate that our costs are 3-5x lower than if we had to pay the direct and indirect costs of owning and managing our own infrastructure and deploying our large array of applications.
- Eric Peng, CEO, PlayMesh

There are also less obvious hidden costs, such as the cost of downtime when one of your administrators makes a mistake configuring your application server and no one can access your Web application for hours. According to a study by Uptime Institute, 70 percent of data center downtime is caused by human error. Consider both the hard costs of downtime, such as lost business and unexpected support costs, and the soft costs, such as idled employees and a tarnished reputation.

 

#4 Get the Best Technology

The benefit of economies of scale doesn’t simply stop at getting the same thing for less money. What you actually end up with is something better, for less money. The stack and platform-level technology you would build yourself will almost never be as good as what a top PaaS will provide. Few companies have both the ability to pay and the attractiveness to hire the world’s best platform builders. The top platform builders are in companies whose main business is platform. People who are world-class in a given discipline for the most part want to work somewhere where that discipline is core to the business, not in an ancillary or supporting role.
A PaaS typically employs specialists who constantly tune, optimize, load-balance, reconfigure, and so on. The result of faster page loads is often a reduction in bounce rates, because customers are more satisfied with the service level they experience. And since search engines use bounce rates and page load times to prioritize paid search rankings, faster application performance can substantially improve your application visibility and business performance.
We’ve mentioned the stack itself several times, and getting the best stack means getting a stack with the latest versions of all components, configured optimally to work with each other and as the foundation for applications such as yours. In addition to the stack itself, there is the deployment mechanism, the platform software that instantiates virtual servers on the infrastructure and installs instances of the stack on them. Many aspects differentiate a good deployment mechanism from a bad one: what configuration parameters are exposed, what component options exist, how stack versions are managed, what activities are automated, what components are pre-built into binaries versus compiled at deployment time, and so on.

With Engine Yard, we can deploy our application in five minutes, and we know we’re running on the best technology stack. If we were managing our own servers, we’d have to take resources away from development to invest in a dedicated IT/infrastructure engineer. Instead, we’re able to focus on building new features.
- Damon Danieli, Founder and CTO, Z2Live

Above all of this, there is the user interface, which may include GUI and CLI variants. Getting the user interface and user experience right is make-or-break for platform interaction. The best platform user interfaces will be simple yet flexible—the things you don’t care to customize shouldn’t get in the way, and the things you do want to customize should be easy to do so. The interface needs to be both learnable and usable—i.e. quick to get started with but also powerful enough to support the expert user.

#5 Stay Up to Date

A particular challenge of deploying your application on a self-built stack is the sheer number of components that need to be tracked, maintained, updated, and re-integrated over time. It’s one thing to get it all set up and humming along in the first place, but the first time you need to swap in an update to the app server or the load balancer or the cache you may find yourself in a nightmare of reconfiguration. One bad experience like this leads many do-ityourselfers to remain indefinitely on an increasingly outdated stack for fear of rocking the boat. The downside of course is that you end up missing out on the latest security updates, performance improvements, and new features— and what may have started as competitive advantage becomes a weighty impediment to keeping up with your competitors.
With PaaS, you not only get the best possible stack as of the moment you deploy, you also get a stack that keeps up with you over time, ensuring that your application is always running on the latest and greatest. You don’t fall behind your competitors, and you also don’t waste time and incur risk by doing it yourself. The PaaS experts constantly incorporate and test component updates and bring them into the platform. At Engine Yard, updates are rolled out in a way that minimizes risk of incompatibility and gives you complete control over how updates are brought into your production applications.

Engine Yard Cloud is a scalable, reliable platform that’s been developed and fine-tuned by cloud experts. We have an easy and repeatable deployment process that is 200% better than managing our own datacenter.
- John Schult, Director of Product Engineering, Vitrue

 

#6 Maximize Uptime

PaaS offerings can help you achieve your availability goals and give you innovative new disaster recovery/ business continuity options. PaaS vendors have the tools, technologies, and experience to help you avoid the unplanned outages that cause downtime. The best PaaS vendors embed technologies and techniques in their products to keep availability high enough that they can offer service-level agreements (SLAs) at or above 99.9% availability. Engine Yard, for example, employs application templates and configuration recipes that minimize human error, ensure up-to-date snapshots of content assets, and allow fast and easy rollbacks if something goes awry.
Beyond basic data backup and OS hardening, PaaS vendors can protect your data in other ways. With Engine Yard, for example, completed transactions can be recovered in the case of database failures, so you never lose data from a committed transaction. And because application configuration is all captured in application templates and recipes, it’s easy to reproduce your application in another availability zone if the primary zone has a disruption. Engine Yard automatically spreads your application across multiple availability zones, enhancing application resilience.

 

#7 Scale Easily

It’s one thing to get the best technology at the best cost for a given size of business. It’s another thing to achieve that at many different sizes—potentially spanning orders of magnitude—as your business grows. When building a platform yourself, you basically have three choices: you can optimize for the scale you’re at now, you can optimize for a scale you expect to be at a later date, or you can invest a lot in building your own scaling mechanism. In the first case you risk having to redo your platform and incur downtime when you outgrow your initial set-up. In the second case you will likely waste resources due to overprovisioning. And in the third case, you will like spend a lot of opportunity cost building something that ends up not nearly as good as what you can get from a PaaS.
With a PaaS, on the other hand, you get the benefit of a great scaling mechanism developed by experts over time and in response to the needs of many customers. On top of that, the PaaS scaling mechanism leverages the underlying infrastructure’s elasticity but presents it in an easy-to-use way, abstracting the complexity of the mechanism’s details. For example, to add instances in the Engine Yard Cloud you simply click the ‘Add’ button, and a wizard walks you through a couple of checkboxes.

We were the victims of our own success—we had so many people using our applications we couldn’t keep up with the need to expand. On top of that, we’re a game studio, not an infrastructure company, so we were inexperienced when it came to configuring servers to scale based on changing traffic patterns. This is where Engine Yard really shines because scaling Rails applications is one of their specialties.
- Eric Peng, CEo, PlayMesh

 

#8 Strengthen Security

Security showcases another distinct advantage of the PaaS model. With the sheer volume and the diversity of security threats on an upward spiral, protecting against attacks is best left to specialists. A PaaS offering provides continual security updates for individual stack components as they are issued. At Engine Yard the stack engineering team maintains fully updated Rails and PHP technologies, so security vulnerabilities in core language or framework components are quickly remedied and customers are automatically notified following the patch.

 

#9 Do Your Project Right

An interesting behavior happens in real-world enterprises when departments or lines of business can’t get corporate approval or fast enough turnaround to build and deploy a new Web application; they tend to do it anyway. Through the back door. They go to a digital media agency; they re-channel some discretionary budget and hire consultants; they get it done using the “easier to get forgiveness than permission” principle.
These unofficial or back-door efforts usually result in a mess, sooner or later. At the very least, they add to the complexity and inefficiency of the environment, because they introduce new and unapproved tools, processes, and/or infrastructure. In other cases they create an even bigger mess: what if the new Web service really takes off, and suddenly the LOB manager needs to procure budget to scale up? What if the new Web service unexpectedly disrupts, corrupts, or causes downtime in legacy applications? It might not be as easy to get “forgiveness” as presumed.

PaaS dramatically cuts the risk, cost, and complexity of new projects. It brings predictability to both the cost and the ramifications of introducing new Web applications and services. To the extent needed, a PaaS offering can complement and add value to existing development and IT operations. Simply put, it doesn’t need to come in through the back door.

 

#10 Get the Best Support

As outlined above, when you build and run on a PaaS, you use technology that has been developed and refined in response to the needs of thousands of customers. But it’s not just the technology that embodies that aggregated expertise. It’s the people themselves. When you call Engine Yard Support, you speak to someone who has dealt with hundreds of problems in the same domain as yours. You speak to someone who has access to—may even be sitting next to—some of the leading experts in the community, whether for core Ruby or PHP language stack components or complementary open source projects.

Read More

What is ERP?

What is ERP?

• Enterprise Resource Planning
• Entirely Refurbished Property
• Exit Return Process
• Enterprise Restructured Personnel 

EXPLANATION

Enterprise resource planning (ERP) is the integrated management of main business processes, often in real-time and mediated by software and technology.
ERP is usually referred to as a category of business management software — typically a suite of integrated applications—that an organization can use to collect, store, manage, and interpret data from these many business activities.
ERP provides an integrated and continuously updated view of core business processes using common databases maintained by a database management system. ERP systems track business resources—cash, raw materials, production capacity—and the status of business commitments: orders, purchase orders, and payroll. The applications that make up the system share data across various departments (manufacturing, purchasing, sales, accounting, etc.) that provide the data.^[1] ERP facilitates information flow between all business functions and manages connections to outside stakeholders.^[2]
Enterprise system software is a multibillion-dollar industry that produces components supporting a variety of business functions. IT investments have become the largest category of capital expenditure in United States-based businesses over the past^[which?] decade. Though early ERP systems focused on large enterprises, smaller enterprises increasingly use ERP systems.^[3]
The ERP system integrates varied organizational systems and facilitates error-free transactions and production, thereby enhancing the organization's efficiency. However, developing an ERP system differs from traditional system development.^[4] ERP systems run on a variety of computer hardware and network configurations, typically using a database as an information repository.[5

Read More

Which of the following protocols can be used by two emails servers to both send and receive email?

Which of the following protocols can be used by two emails servers to both send and receive email?

• POP3
• IMAP4
• SMTP
• HTTPS

EXPLANATION

What Is IMAP?

IMAP(Internet Message Access Protocol) is the protocol used by the vast majority of consumer email accounts. With IMAP, emails are stored on an Internet server. When a user accesses their account, they’re connected to the external server, and data is transferred from the server to their local machine – which itself doesn’t actually receive any email messages.
One of the key advantages of IMAP – aside from remote access – is that it allows a single account to be operated and managed by multiple users, without the need for a complex workaround. It can also put a fair amount of strain on your mail server, if your business manages its own email service.
In order for IMAP to function, it requires one of two ports to be open:

• Port 143: The default IMAP port; this allows the protocol to listen for incoming requests to synchronize emails. Traffic through this port is unencrypted.
• Port 993: Used for IMAP over SSL.

What Is POP3?

Unlike IMAP, POP3 (Post Office Protocol 3) downloads messages from a mail service to a user’s local computer. This allows the user to not only receive emails on their own machine, but also to disconnect from the Internet and retain access to all of their messages. There are a number of advantages to this approach.
First and foremost, unless you’re opting to leave a copy of each email on the mail server, it clears up a significant amount of space by storing all files on the user’s local machine. This makes it much easier to back up one’s email messages, in addition to making search and organization far more efficient.
Unfortunately, POP3 isn’t without its weaknesses either. The protocol by default assumes that only a single user will be accessing a particular email account, meaning that you’ll need a workaround if you want multiple users on a single email. In addition, remote access can be something of a problem. Finally, the fact that most POP services delete downloaded emails from the server by default makes it incredibly difficult to synchronize an account to multiple machines.
POP3 requires one of the following two ports to be open:

• Port 110: For unencrypted POP3 access; this is the default listening/communications port.
• Port 995: Used for encrypted POP3 connections.

Which One Should You Use?

And now for the million dollar question…which of the two protocols should your business use?
The short answer is IMAP. Given the wealth of different devices typically used by modern employees, the capacity to remotely access one’s email regardless of location is absolutely essential.  The longer answer is that – as always – it depends entirely on what you need email for.
The truth is, there’s really nothing stopping you from using multiple protocols to access an email account – the technology does exist to do so, after all.

Sending Email: SMTP And HTTP

What Is SMTP?

Now, though there are two protocols associated with receiving emails, there’s really only one associated with sending them. SMTP(Simple Mail Transfer Protocol) is the gold standard for passing email messages from one mail server to another. Every email service uses some variation of this protocol.
There’s one more difference between SMTP and IMAP/POP3: unlike the latter two, it requires no authentication to function. Although modern SMTP applications restrict relaying, this nevertheless allows for a fair volume of spam to exist on the web; some tech-savvy criminals can even send emails using another’s account.
There are two ports you’ll need to be aware of for SMTP:

• Port 25: This is the default SMTP port. It is not encrypted.
• Port 465 / 587: The default port for using SMTP through SSL.

In addition, some hosts may offer a secondary port as an alternative to clients for whom port 25 is filtered.  

What Does HTTP Have To Do With Emails?

Now, granted, I’m certain a few of you are at least a little surprised to see HTTP (Hyper Text Transfer Protocol) included on this list. After all, it’s not really involved in the process of sending or receiving an email, nor does it directly interact with any of the other mail protocols. So…what does it have to do with email, exactly?
Easy – HTTP (and its more secure cousin, HTTPS) is the means by which you’re probably going to access your mailbox, particularly if you’re using a web-based email service like Hotmail or Gmail. For that reason, it actually occupies a fairly important position in the grand scheme of things, even if it’s not technically a mail protocol itself.

 

Read More

Which email protocol is used to store incoming emails on a mail server?

Which email protocol is used to store incoming emails on a mail server?

• SMTP
• POP3
• HTTP
• IMAP

EXPLANATION

As its name implies, IMAP allows you to access your email messages wherever you are; much of the time, it is accessed via the Internet. Basically, email messages are stored on servers. Whenever you check your inbox, your email client contacts the server to connect you with your messages. When you read an email message using IMAP, you aren't actually downloading or storing it on your computer; instead, you are reading it off of the server. As a result, it's possible to check your email from several different devices without missing a thing.

Read More