Sql Server Interview Questions on File Server and Client Server Database

Two of the main things, the data of this approach is working. The work of these two different ways.

The approach of the database file server, data stored in a file, users need to get data directly from a file. Directly changed when the file is open is made on the application. Data files and writes these files. If the user data 10 and 10 who have been working to write the file.

In the client-server approach is still the data is stored in a file, but from a server, all servers in the access control hand. When to apply for any would like to use existing data, and then use the application send a request to the server. To read later, the server requests and send feedback. When to apply for any you want to write the request in the file sent to the server on the server, something written on the document. A person from the read and write data files.

Oracle, Informix, Microsoft SQL Server are the best suit for example, client-server databases. Single-user desktop, such as Microsoft Access.

There are lots of advantages of client server databases.

Changes or accidental crash data) less chance of data read and write a single program.
2) Only single program play good role of security so enforcement of security is easy.
3) and more efficient client-server databases, database files using the server's network bandwidth.
4) All things are handling by single computes so performance is good and quite impressive.
5) The client-server database on the use of some good features, like a record transactions and to protect the disk and network errors, restore our data.

Some of these features also in the file server approach can be used, you need these more expensive client-server market. Also, you can learn a dot net interview questions for many.

10 Tips For Writing An E-Learning RFP / RFQ

In assessing the many types of products and services, companies or organizations sometimes use an RFP proposal (request) / RFQ (request for quotation) process. There are challenges associated with rifampicin / inquiry process, for example, may need the length of time, its complexity, and so on. Many companies turned to the use of invitations to tender explicit / inquiry process which is based on the above reasons, as well as a host of other issues does not belong to the subject of this article.

Just writing an e-Learning / Learning Management Systems RFP / RFQ can be a pretty daunting job. The task of putting together a good e-Learning RFP / RFQ is exacerbated because Learning Management Systems software and e-Learning Solutions can possess many layers of complexity, especially when they are developed to integrate with and meet the needs of your organization's information technology backbone.

Communicating your company's needs is often difficult. The tips below are by no means exhaustive, as they are designed to give you some suggestions and information to help you with writing an e-Learning / Learning Management System software RFP / RFQ.

1. You and your company should perform a thorough internal and external needs assessment, research, and planning long before you sit down to write your e-Learning / Learning Management Systems RFP / RFQ. A whitepaper I wrote a few years back, called ‘e-Learning Best Practices' that is available at http://www.syberworks.com/articles/Bestpractices.pdf. It has a section on ‘Scoping Out your e-Learning Needs', and other information, which will provide you some information and guidelines for this part of the process.

2. If possible, try to write in a group context, or at least, access to colleagues, your boss, or your assistant is another set of files the eye. RFP / RFQs there is a tendency, that is a long-term, complex, involving documents, so let others view your work is very useful. This is when a better principle or stakeholders more help with writing e-learning / learning management systems tenders / inquiry.

3. Provide a company background statement that is specific and gives potential vendor companies information that is useful. It's fine to pull your company background statement from your marketing material, but don't stop there. If your e-Learning initiative will serve several departments, it might be a good idea to provide some sort of an organizational framework in your RFP / RFQ with a little history to help fill in the pieces of the puzzle.

4. Supply a statement of work that is specific and gives potential vendor companies information they will need. Sometimes a company will cut and paste their training department's goals and objectives into the statement of work. While this is helpful information to a point, too much information of this type may throw a potential vendor off course, which may result in you receiving proposals that do not meet your needs.

The problem is that people can have the tendency to lump goals, objectives, and tactics in the same category, but ultimately, they are not the same. There is a difference between a set of tactics verses a set of objectives verses a set of goals. A group of tactics can be the mechanism by which an objective is achieved. Objectives can monetize, quantify, and delineate desired outcomes to achieve a stated goal or goals.

Its important to remember that an e-Learning solution / Learning Management System is a tool used to achieve and / or promote a various set tactics as part of an entire training strategy which ideally, should be in line with company or department goals. Since it is a tool that is executed and used as part of a tactic, be sure to provide enough detailed information that is specific to your desired uses of an e-Learning solution along with your department's goals and objectives.

5. Develop a set of user personas so potential vendor companies will be given framework as to how their system will be used by every person that will touch it at your organization. Provide a breakdown of technical skill required for each user persona, including the technical requirements of any other IT systems they would use and need to be integrated into the e-Learning Solution / Learning Management System technology.

For example, a Human Resources Manager may work with an HRIS (Human Resources Information System) that would need to integrated with the Learning Management System. Be sure to provide the platform type, version, underlying database technology, the file structure, and any other information that is useful to the potential vendor company.

6. Prioritize features and functionality into a hierarchy based on the concepts of absolutely must have (priority 1), would like to have (priority 2), nice to have but not necessary (priority 3), or something along these lines to demonstrate level of importance to the vendor companies that will submit proposals for your RFP / RFQ.

Be sure to explain the features and functionality you require in concise and complete sentences. Features and functionality displayed in lists of three or four word bullet points often falls short of really explaining what your requirements are and can cost you more time further down the road.

7. Ask for and include sections for ‘RFP / RFQ boilerplate' type of information. Some are listed below:

Vendor Information-Your RFP / RFQ should contain a vendor information section that details all contact information, company size, public or private, the number of years in business, etc. You may also want to ask for financial information. *

*It's important to remember that company financials can be relevant information for your firm to have when evaluating a vendor; but they are not a consistent indicator of a company or product's longevity or market staying power, especially in technology industries. Venture funded or publicly traded firms are often bought and sold to pay off investors, eliminate competing technology platforms, and for other reasons.

The e-Learning / Learning Management Systems industry continues to experience lots of consolidation and many industry analysts predict this trend will continue. For example in the last twelve months, Saba bought Centra Software and Blackboard acquired Web CT.

General product / service information in this chapter are general information about the proposed system as the release date, version, number of users, the number of years in operation, server platform, database, Java clients, browser compatibility, any licensing -- , support and maintenance contracts and more. It's also good to ask how the potential provider company differentiates itself from its competitors and includes a list of all URLs, usernames and passwords for the demo version of their product.

Reference Information-This section is an area for the potential vendor company to list three or more reference customers and a partial list of clients.

8. Provide a place for the prospective vendor company to detail their proposed solution. It should cover in detail the product; pricing; its implementation; IT platform requirements; licensing or hosting requirements; system configuration; testing; user loading; HRIS data loading; interfaces between software applications that need to be developed; acceptance testing; general functionality; priority 1, 2, and 3 features and functionality (as discussed in #6); user hierarchies; localization; course and curriculum administration; system administration; authoring tools; system and authoring tool training; project plan and timelines; maintenance; support; and more.

9. Create a question and answer section for the prospective vendor company. The question and answer section contain questions about the technology; system requirements; project implementation; time needed for implementation; testing acceptance period; or another types of questions that are specific and germane to e-Learning solutions / Learning Management Systems implementation initiative.

10. Clearly identify the number of copies, formats, submission dates, locations where the proposal should be sent, and next steps. Be sure to include a date as to when you will be choosing your shortlist for the next round of evaluation.