Creating Custom Toolbars =
Just as menu bars are staples for keyboard users.toolbars are used by mouse-oriented users to quickly execute functions of your applications.Think of toolbars as mouse shorcuts. In general you should have one toolbar for every menu in your program.When you display a menu you should also display a corresponding toolbar.
A toolbars dialog box shows you a list of all toolbars access. You can use it to
>Customize an existing toolbar
>Create a new toolbar
>Select color or black-abnd-white buttons
>Select large orsmall buttons
>Choose to display tooltips
All currently displayed toolbars have a check mark next to thier names.
To customize a toolbar. the toolbar must be displayed. To display a toolbar.Click on the check box to the toolbar you want to display.When all the toolbars you want to customize are displayed.
=cstomizing a toolbar consists of four basic function:
>Adding buttons to toolbars
>Removing buttons from toolbars
>Moving the face (image)of toolbar buttons
Adding Buttons to a toolbar =
To customize toolbars dialog box
>A category list
>A view of all or objects for the selected category
Removing buttons from a toolbar=
>The function isn't used
>A toolbutton that is used morte frequently will replace it.
>Users shoudn't be allowed to perform the function.
Moving buttons on toolbar=
You can move toolbuttons on a toolbar or move buttons from one toolbar to another. You should always attempt to place toolbuttons into logical groups.
Example: Microsoft Word separates paragraph alingment buttons from text formatting buttons.
Changing button faces on toolbars
There are three merhods for customizing the image of a toolbuttons.
>Copy and Paste an image using the clipboard.
>Select a bitmap from access supplied images
>Using an image using the built in Button Editor.
Copy and Paste an image by using the clipboard
1.Display the image in the graphic editor of your choice
2. Use the editor's function to copy the inage to the clipboard
3. Open the shorcut menu of the toolbutton you ant to change
4. Select Paste Button image
You can also copy the image from one toolbutton to another.to do this
1.Open the shorcut menu of the toolbutton you want to copy the image from
2.Select Copy button aimage
3. Open the shorcut menu of the toolbutton you want to change
4. Select Paste button image
Hiding Access displaying toolbars=After you have defined all the toolbars for you application you need to control when and which toolbars are shown to. Toolbars can be hidden or shown any time using the the show.
Allowing users to modify your custom toolbars=
1.Uncheck the allow toolbar changes box on the application srartup dialog box
2.Set allow toolbar changes proverty of the sApplication objject to false.
Monday, January 25, 2010
Wednesday, December 9, 2009
ASSIGN_02
TWO ARTICLES RE OF DATABASE
SQL Azure with ASP Dot Net
By Don Schlichting
Introduction
SQL Azure (SSDS - SQL Server Data Services) is a cloud database system offered by Microsoft. We interact with the SQL Azure services by either issuing statements to it though a command prompt or developing Dot Net applications. This article will introduce and demonstrate development of SQL Azure ASP Dot Net applications.
Connecting
Connecting to SQL Azure is similar to connecting to a traditional SQL Server. A connection string is created then opened. To begin with SQL Azure, create an account from the Microsoft Azure web site. Once the account is created, log in and navigate to the Server Administration page. Select the master database (master is automatically created for us when the Azure account is created), and then select “Connection Strings”. A popup will display the connection string for ADO Dot Net and ODBC. Copy the ADO Dot Net string. On the next tab, Firewall Settings, create a rule to allow your client machine access as shown below.
To Partition or Not to Partition in E-Business Suite
By Steve Callan
As a database administrator, there are two kinds of databases you are likely to own: those you design and those you inherit. In this article, we’ll look at what takes place during the design phase, and then apply the lessons there to a real world implementation, courtesy of Oracle E-Business Suite.
As many database design books tend to illustrate, there are two structures to keep in mind when designing a database, and those are logical and physical. The logical structure is usually what comes to mind when visualizing a layout, where the visual image is materialized into an entity relation diagram (ERD) courtesy of a tool. The logical layout helps to diagram how the database (or more specifically, the application) will operate. Details filled in here include how tables are organized with respect to attributes. As an example, if you have a table dealing with people, how are those people further classified? You could have one table “managing” everything about people, regardless of where they exist (i.e., internal or external to your organization).
In this super table, using employees and customers as a simple classification, not all columns or attributes apply to a person (would an employee have a shipping address versus would a customer have a hire date?). If you prefer to segregate people, then two tables could be used. This approach leads to more tables (it can be applied to more than just people), but there are benefits related to performance since there are smaller sets of data to examine (which leads to a hint where this is going).
Continuing on, once all the tables are designed, what happens next is table creation. The big mistake or hobbling event here is that the physical table is created as a direct mapping of the logical table. In other words, you could look at many databases and see a direct mapping of the ERD/logical table in the physical structure of the database. The pitfall here is that the physical design often fails to take performance-enhancing features into account. The functional layout may be quite valid, but the physical layout has immediately introduced obstacles to good or acceptable performance.
A classic example of this involves partitioning, or the lack thereof. This is less likely to happen during the design of a data warehouse because by now, the inclusion of partitioning in a warehouse is a common, well-known practice. However, this is not always the case in non-warehouse databases, where partitioning can certainly help improve performance and make administration easier to perform. Most tables are heap tables, and the term heap connotes a pile, and that is what most databases are: a pile of tables.
Other types of tables to consider when going from the logical to the physical include index organized tables. An ERD-diagrammed picture of a table isn’t necessarily going to tell you “make this table IOT when you create it.” Other table options are available, such as external, temporary, and object (why would you ever use that?), so keep them in mind before blindly laying down a logical table into a physical one without any other considerations.
That consideration seems like a fairly common sense approach, but sometimes common sense loses out to cents, as in paying much more for a feature that would make an application run better in the first place. This brings us to the Oracle Applications/E-Business Suite tie-in where the logical is the physical, unless you pay more to make the physical perform better. How and why do we know this?
Oracle Support has published a 53-page document regarding the use of partitioning within EBS (Using Database Partitioning with Oracle E-Business Suite, An Oracle White Paper, March 2009). This white paper updates/replaces the first version published in February, 2008 (with the slightly different title of Database Partitioning for Oracle E-Business Suite). The majority of the white paper explains what partitioning is and how to use it, which is basically a repeat of what is already contained in “real world” Oracle documentation (as opposed to “Oracle Apps world” documentation). If you are already familiar with partitioning, the relevant part of the white paper is the table titled “Examples of Partition Keys for Oracle Application Tables.”
The suggestion for partitioning encompass ten tables, along with the type of partitioning and the partitioning key (one table is listed twice). So, does Oracle Apps have any partitioning or is what is listed in the white paper a drill in implementing this feature from scratch? The answer to both is yes. In version 11.5.10, and excluding SYSTEM, 110 tables are partitioned. These tables install that way by default, and do not support user modification. By not supported, what is meant is this:
Modifying existing base product indexes and tables that have already been partitioned is not recommended or supported as it can cause application errors.
So, supported means you can add custom partitioning, but don’t mess with existing partitioned objects. The other tables, the list of which being a starting point and not meant to be all inclusive, are left for you to transform from normal tables to partitioned tables (and don’t forget to consider partitioned indexes).
Taking the list of tables and doing a look-see of what’s in an existing implementation (an 11.5.10 database), the results show some moderately sized tables. Note: not all tables may appear as this depends on additional modules you have licensed.
SQL Azure with ASP Dot Net
By Don Schlichting
Introduction
SQL Azure (SSDS - SQL Server Data Services) is a cloud database system offered by Microsoft. We interact with the SQL Azure services by either issuing statements to it though a command prompt or developing Dot Net applications. This article will introduce and demonstrate development of SQL Azure ASP Dot Net applications.
Connecting
Connecting to SQL Azure is similar to connecting to a traditional SQL Server. A connection string is created then opened. To begin with SQL Azure, create an account from the Microsoft Azure web site. Once the account is created, log in and navigate to the Server Administration page. Select the master database (master is automatically created for us when the Azure account is created), and then select “Connection Strings”. A popup will display the connection string for ADO Dot Net and ODBC. Copy the ADO Dot Net string. On the next tab, Firewall Settings, create a rule to allow your client machine access as shown below.
To Partition or Not to Partition in E-Business Suite
By Steve Callan
As a database administrator, there are two kinds of databases you are likely to own: those you design and those you inherit. In this article, we’ll look at what takes place during the design phase, and then apply the lessons there to a real world implementation, courtesy of Oracle E-Business Suite.
As many database design books tend to illustrate, there are two structures to keep in mind when designing a database, and those are logical and physical. The logical structure is usually what comes to mind when visualizing a layout, where the visual image is materialized into an entity relation diagram (ERD) courtesy of a tool. The logical layout helps to diagram how the database (or more specifically, the application) will operate. Details filled in here include how tables are organized with respect to attributes. As an example, if you have a table dealing with people, how are those people further classified? You could have one table “managing” everything about people, regardless of where they exist (i.e., internal or external to your organization).
In this super table, using employees and customers as a simple classification, not all columns or attributes apply to a person (would an employee have a shipping address versus would a customer have a hire date?). If you prefer to segregate people, then two tables could be used. This approach leads to more tables (it can be applied to more than just people), but there are benefits related to performance since there are smaller sets of data to examine (which leads to a hint where this is going).
Continuing on, once all the tables are designed, what happens next is table creation. The big mistake or hobbling event here is that the physical table is created as a direct mapping of the logical table. In other words, you could look at many databases and see a direct mapping of the ERD/logical table in the physical structure of the database. The pitfall here is that the physical design often fails to take performance-enhancing features into account. The functional layout may be quite valid, but the physical layout has immediately introduced obstacles to good or acceptable performance.
A classic example of this involves partitioning, or the lack thereof. This is less likely to happen during the design of a data warehouse because by now, the inclusion of partitioning in a warehouse is a common, well-known practice. However, this is not always the case in non-warehouse databases, where partitioning can certainly help improve performance and make administration easier to perform. Most tables are heap tables, and the term heap connotes a pile, and that is what most databases are: a pile of tables.
Other types of tables to consider when going from the logical to the physical include index organized tables. An ERD-diagrammed picture of a table isn’t necessarily going to tell you “make this table IOT when you create it.” Other table options are available, such as external, temporary, and object (why would you ever use that?), so keep them in mind before blindly laying down a logical table into a physical one without any other considerations.
That consideration seems like a fairly common sense approach, but sometimes common sense loses out to cents, as in paying much more for a feature that would make an application run better in the first place. This brings us to the Oracle Applications/E-Business Suite tie-in where the logical is the physical, unless you pay more to make the physical perform better. How and why do we know this?
Oracle Support has published a 53-page document regarding the use of partitioning within EBS (Using Database Partitioning with Oracle E-Business Suite, An Oracle White Paper, March 2009). This white paper updates/replaces the first version published in February, 2008 (with the slightly different title of Database Partitioning for Oracle E-Business Suite). The majority of the white paper explains what partitioning is and how to use it, which is basically a repeat of what is already contained in “real world” Oracle documentation (as opposed to “Oracle Apps world” documentation). If you are already familiar with partitioning, the relevant part of the white paper is the table titled “Examples of Partition Keys for Oracle Application Tables.”
The suggestion for partitioning encompass ten tables, along with the type of partitioning and the partitioning key (one table is listed twice). So, does Oracle Apps have any partitioning or is what is listed in the white paper a drill in implementing this feature from scratch? The answer to both is yes. In version 11.5.10, and excluding SYSTEM, 110 tables are partitioned. These tables install that way by default, and do not support user modification. By not supported, what is meant is this:
Modifying existing base product indexes and tables that have already been partitioned is not recommended or supported as it can cause application errors.
So, supported means you can add custom partitioning, but don’t mess with existing partitioned objects. The other tables, the list of which being a starting point and not meant to be all inclusive, are left for you to transform from normal tables to partitioned tables (and don’t forget to consider partitioned indexes).
Taking the list of tables and doing a look-see of what’s in an existing implementation (an 11.5.10 database), the results show some moderately sized tables. Note: not all tables may appear as this depends on additional modules you have licensed.
Wednesday, November 18, 2009
ASSIGN_01
Contrast Hierarchical and Relational Database
A.) Hierarchical Database
A database organization method that is structured in a hierarchy. All access to data starts at the top of the hierarchy and moves downward; for example, from customer to orders, vendor to purchases, etc. Contrast with relational database and network database.
B.) Relational Database
A relational database matches data by using common characteristics found within the data set. The resulting groups of data are organized and are much easier for people to understand.
For example, a data set containing all the real-estate transactions in a town can be grouped by the year the transaction occurred; or it can be grouped by the sale price of the transaction; or it can be grouped by the buyer's last name; and so on.
Such a grouping uses the relational model (a technical term for this is schema). Hence, such a database is called a "relational database."
The software used to do this grouping is called a relational database management system. The term "relational database" often refers to this type of software.
Relational databases are currently the predominant choice in storing financial records, manufacturing and logistical information, personnel data and much more.
A.) Hierarchical Database
A database organization method that is structured in a hierarchy. All access to data starts at the top of the hierarchy and moves downward; for example, from customer to orders, vendor to purchases, etc. Contrast with relational database and network database.
B.) Relational Database
A relational database matches data by using common characteristics found within the data set. The resulting groups of data are organized and are much easier for people to understand.
For example, a data set containing all the real-estate transactions in a town can be grouped by the year the transaction occurred; or it can be grouped by the sale price of the transaction; or it can be grouped by the buyer's last name; and so on.
Such a grouping uses the relational model (a technical term for this is schema). Hence, such a database is called a "relational database."
The software used to do this grouping is called a relational database management system. The term "relational database" often refers to this type of software.
Relational databases are currently the predominant choice in storing financial records, manufacturing and logistical information, personnel data and much more.
Sunday, August 16, 2009
my_idea_Is
A.Discuss what have you learn and undestood what is relationship of DBMS,so far?
The DBMS is interact to the computer system to store data,is just an application that let you store the informatiojn of database and responsible to build the database,storage devices to build data structure in order you to have database.The DBMS to maintain the data structure,data,database.
The data is a representation of facts,concepts or instructions in a formalized manner suitable for communication,interpretation or processing by human beings or by automatic means.Well managed data can save time,money,increase productivity.
Database-A computer database is a program that lets you store,manage and manipulate data.
B.Define how each of the following fit and function within the framework of relational DBMS system:
1.)key fields -primary key,foreign key
2.)Database Records-holds record of the database
3.)Data Queries-allows us to store data in different ways
4.)Data types-
5.)Data forms-allows us to build a user-friendly interface for our user
6.)Tables/Database-allowa to make a table in plan our database
7.)Relationships(table linkages)-allow us to format a data in table for linkages
The DBMS is interact to the computer system to store data,is just an application that let you store the informatiojn of database and responsible to build the database,storage devices to build data structure in order you to have database.The DBMS to maintain the data structure,data,database.
The data is a representation of facts,concepts or instructions in a formalized manner suitable for communication,interpretation or processing by human beings or by automatic means.Well managed data can save time,money,increase productivity.
Database-A computer database is a program that lets you store,manage and manipulate data.
B.Define how each of the following fit and function within the framework of relational DBMS system:
1.)key fields -primary key,foreign key
2.)Database Records-holds record of the database
3.)Data Queries-allows us to store data in different ways
4.)Data types-
5.)Data forms-allows us to build a user-friendly interface for our user
6.)Tables/Database-allowa to make a table in plan our database
7.)Relationships(table linkages)-allow us to format a data in table for linkages
Thursday, July 2, 2009
MY_ASSIGNMNT
A. What are data types?
A data type in a programming language is a set of data with values having predefined characteristics. Examples of data types are: integer, floating point unit number, character, string, and pointer. Usually, a limited number of such data types come built into a language. The language usually specifies the range of values for a given data type, how the values are processed by the computer, and how they are stored.With object-oriented programming, a programmer can create new data types to meet application needs. Such an exercise as known as "data abstraction" and the result is a new class of data. Such a class can draw upon the "built-in" data types such as number integers and characters. For example, a class could be created that would abstract the characteristics of a purchase order. The purchase order data type would contain the more basic data types of numbers and characters and could also include other object defined by another class. The purchase order data type would have all of the inherent services that a programming language provided to its built-in data types.Languages that leave little room for programmers to define their own data types are said to be strongly-typed languages.
B. What role do they play in a database?
Data Types -- The Easiest Part of Database DesignDatabase design can be very complicated, and it truly is an art as opposed to a science; sometimes there are multiple correct ways to model the same data with pros and cons to each. I can understand that normalization can be tricky to comprehend and to implement, and that concepts like stored procedures and foreign keys and even indexes and constraints can take time to grasp.But -- what about Data Types? They are so basic, so simple, so fundamental; not only for database design, but for any sort of programming in general ... what excuse is there for not using correct data types for the columns in a table design?I see it time and time again in the SQLTeam forums -- "dates" that don't sort properly, "numbers" that don't add correctly, "boolean" columns containing 10 different values, invalid entries that somehow show up in "date" columns, and so on ... Of course, since we are rarely provided any DDL to review, it often takes dozens of posts going back and forth until we finally realize: "wait ... you aren't using a datetime data type to store these dates??? Arggh!!"In short, even a poorly designed database, with one giant "master" table with no normalization or logic anywhere in sight, should still at least use a Money data type to store currency values!Perhaps the confusion comes from Excel users, where data types are handled behind the scenes ... or maybe "old school" VB programmers used to using variant data types (or worse -- undeclared variables!) to store values... But when you design a table in any database, you are always explicitly stating the data types of the columns -- there's nothing hidden, or no option to ignore them. You must declare a data type when creating a column, so how can anyone justify using VARCHAR to store a date?
C. Enumerate 3 data types of DBMS and explain.
1. Fixed-length textThe char data type is used to store fixed-length text with up to 255 characters. Specifying the number of characters to store limits how big the column will be. Text values retrieved from a char column are padded with spaces, if necessary, to the size of the column. The char data type is not available from the Access designer.The following statement creates a table with a 10-character text column and a 255-character text column, both with Unicode compression:CREATE TABLE T1 (c1 char(10) WITH compression, c2 char WITH compression)2. Variable-length textThe varchar data type is used to store variable-length text with up to 255 characters.Text values retrieved from a varchar column are trimmed of any trailing spaces.The following statement creates a table with a 10-character text column and a 255-character text column, both with Unicode compression:CREATE TABLE T2 (c1 varchar(10) WITH compression, c2 varchar WITH compression)3. Text BLOBThe longchar data type is used to store variable-length text with an unspecified number of characters, limited only by the maximum size of JET database files (2 GB – about 1 billion uncompressed Unicode characters).Some software libraries are able to handle longchar columns as basic text columns, but others must use BLOB techniques for accessing their data. In particular, the ADO components so often used in Visual Basic, VBA and ASP applications can access longchar columns as basic text when using the JET 4.0 OLE-DB provider to access the database, but must use BLOB handling routines (GetChunk / AppendChunk) when using an ODBC connection.The following statement creates a table with two variable-length text BLOB columns, both with Unicode compression:
A data type in a programming language is a set of data with values having predefined characteristics. Examples of data types are: integer, floating point unit number, character, string, and pointer. Usually, a limited number of such data types come built into a language. The language usually specifies the range of values for a given data type, how the values are processed by the computer, and how they are stored.With object-oriented programming, a programmer can create new data types to meet application needs. Such an exercise as known as "data abstraction" and the result is a new class of data. Such a class can draw upon the "built-in" data types such as number integers and characters. For example, a class could be created that would abstract the characteristics of a purchase order. The purchase order data type would contain the more basic data types of numbers and characters and could also include other object defined by another class. The purchase order data type would have all of the inherent services that a programming language provided to its built-in data types.Languages that leave little room for programmers to define their own data types are said to be strongly-typed languages.
B. What role do they play in a database?
Data Types -- The Easiest Part of Database DesignDatabase design can be very complicated, and it truly is an art as opposed to a science; sometimes there are multiple correct ways to model the same data with pros and cons to each. I can understand that normalization can be tricky to comprehend and to implement, and that concepts like stored procedures and foreign keys and even indexes and constraints can take time to grasp.But -- what about Data Types? They are so basic, so simple, so fundamental; not only for database design, but for any sort of programming in general ... what excuse is there for not using correct data types for the columns in a table design?I see it time and time again in the SQLTeam forums -- "dates" that don't sort properly, "numbers" that don't add correctly, "boolean" columns containing 10 different values, invalid entries that somehow show up in "date" columns, and so on ... Of course, since we are rarely provided any DDL to review, it often takes dozens of posts going back and forth until we finally realize: "wait ... you aren't using a datetime data type to store these dates??? Arggh!!"In short, even a poorly designed database, with one giant "master" table with no normalization or logic anywhere in sight, should still at least use a Money data type to store currency values!Perhaps the confusion comes from Excel users, where data types are handled behind the scenes ... or maybe "old school" VB programmers used to using variant data types (or worse -- undeclared variables!) to store values... But when you design a table in any database, you are always explicitly stating the data types of the columns -- there's nothing hidden, or no option to ignore them. You must declare a data type when creating a column, so how can anyone justify using VARCHAR to store a date?
C. Enumerate 3 data types of DBMS and explain.
1. Fixed-length textThe char data type is used to store fixed-length text with up to 255 characters. Specifying the number of characters to store limits how big the column will be. Text values retrieved from a char column are padded with spaces, if necessary, to the size of the column. The char data type is not available from the Access designer.The following statement creates a table with a 10-character text column and a 255-character text column, both with Unicode compression:CREATE TABLE T1 (c1 char(10) WITH compression, c2 char WITH compression)2. Variable-length textThe varchar data type is used to store variable-length text with up to 255 characters.Text values retrieved from a varchar column are trimmed of any trailing spaces.The following statement creates a table with a 10-character text column and a 255-character text column, both with Unicode compression:CREATE TABLE T2 (c1 varchar(10) WITH compression, c2 varchar WITH compression)3. Text BLOBThe longchar data type is used to store variable-length text with an unspecified number of characters, limited only by the maximum size of JET database files (2 GB – about 1 billion uncompressed Unicode characters).Some software libraries are able to handle longchar columns as basic text columns, but others must use BLOB techniques for accessing their data. In particular, the ADO components so often used in Visual Basic, VBA and ASP applications can access longchar columns as basic text when using the JET 4.0 OLE-DB provider to access the database, but must use BLOB handling routines (GetChunk / AppendChunk) when using an ODBC connection.The following statement creates a table with two variable-length text BLOB columns, both with Unicode compression:
Saturday, June 27, 2009
MV vs. DATAF
Characteristics of Memory Variable:
* Memory variable files are a way to store the status of memory variables that are currently stored in memory and use them later in the same program or in another session of FoxPro.
The memory location holds values- perhaps numbers or text or more complicated types of data like a payroll record. Operating Systems load programs into different parts of RAM so there is no way of knowing exactly which memory location will hold a particular variable before the program is run. By giving a variable a symbolic name like "employee_payroll_id" the compiler or interpreter can always work out where to store the variable in memory.
Characteristics of Data Field:
* A data field is the smallest subdivision of the stored data that can be accessed. A data field can be used to store numerical information such as price, count or a date or time, or even a data and time. A pair of data fields can be used in combination to hold a geo-spatial coordinate. Also, a data field can be used to hold a block of text. A data field takes up permanent storage within the data-store. The field may contain data to be entered as well as data to be displayed.
* Memory variable files are a way to store the status of memory variables that are currently stored in memory and use them later in the same program or in another session of FoxPro.
The memory location holds values- perhaps numbers or text or more complicated types of data like a payroll record. Operating Systems load programs into different parts of RAM so there is no way of knowing exactly which memory location will hold a particular variable before the program is run. By giving a variable a symbolic name like "employee_payroll_id" the compiler or interpreter can always work out where to store the variable in memory.
Characteristics of Data Field:
* A data field is the smallest subdivision of the stored data that can be accessed. A data field can be used to store numerical information such as price, count or a date or time, or even a data and time. A pair of data fields can be used in combination to hold a geo-spatial coordinate. Also, a data field can be used to hold a block of text. A data field takes up permanent storage within the data-store. The field may contain data to be entered as well as data to be displayed.
Sunday, June 21, 2009
ITS 121B TERM CONTRAST
A.Data vs. Information
=Data: (ISO) A representation of facts, concepts or instructions in a formalised manner suitable for communication, interpretation or processing by human beings or by automatic means.Letters, numbers, colours, symbols, shapes, temperatures, sound or other facts and figures are data suitable for processing.
Information: (ISO) The meaning that is applied to data by means of the conversions applied to that data. I.E. processed data.
Data
Raw material for computer processing for example, numbers, text, images, and sounds, in a form that is suitable for storage or processing by a computer.
• The ability to gather, store, process, and retrieve data in a timely manner is vital
• Well managed data can
– save time and money
– increase productivity
– enhance decision making
Information
Computer data that has been organized and presented in a systematic fashion to clarify the underlying meaning.
=Data: (ISO) A representation of facts, concepts or instructions in a formalised manner suitable for communication, interpretation or processing by human beings or by automatic means.Letters, numbers, colours, symbols, shapes, temperatures, sound or other facts and figures are data suitable for processing.
Information: (ISO) The meaning that is applied to data by means of the conversions applied to that data. I.E. processed data.
Data
Raw material for computer processing for example, numbers, text, images, and sounds, in a form that is suitable for storage or processing by a computer.
• The ability to gather, store, process, and retrieve data in a timely manner is vital
• Well managed data can
– save time and money
– increase productivity
– enhance decision making
Information
Computer data that has been organized and presented in a systematic fashion to clarify the underlying meaning.
B.Computer storage vs.Data Storage
=
Data storage vs. computer storage
Computer data storage
computer data storage, often called storage or memory, refers to computer components, devices, and recording media that retain digital data used for computing for some interval of time. Computer data storage provides one of the core functions of the modern computer, that of information retention. It is one of the fundamental components of all modern computers, and coupled with a central processing unit (CPU, a processor), implements the basic computer model used since the 1940s.
In contemporary usage, memory usually refers to a form of semiconductor storage known as random access memory (RAM) and sometimes other forms of fast but temporary storage. Similarly, storage today more commonly refers to mass storage - optical discs, forms of magnetic storage like hard disks, and other types slower than RAM, but of a more permanent nature. Historically, memory and storage were respectively called primary storage and secondary storage.
The contemporary distinctions are helpful, because they are also fundamental to the architecture of computers in general. The distinctions also reflect an important and significant technical difference between memory and mass storage devices, which has been blurred by the historical usage of the term storage. Nevertheless, this article uses the traditional nomenclature.
Any data storage device; that records (stores) or retrieves (reads) information (data) from any medium, including the medium itself. A data storage device is a device for recording (storing) information (data). Recording can be done using virtually any form of energy, spanning from manual muscle power in handwriting, to acoustic vibrations in phonographic recording, to electromagnetic energy modulating magnetic tape and optical discs.
A storage device may hold information, process information, or both. A device that only holds information is a recording medium. Devices that process information (data storage equipment) may either access a separate portable (removable) recording medium or a permanent component to store and retrieve information.
Data storage vs. computer storage
Computer data storage
computer data storage, often called storage or memory, refers to computer components, devices, and recording media that retain digital data used for computing for some interval of time. Computer data storage provides one of the core functions of the modern computer, that of information retention. It is one of the fundamental components of all modern computers, and coupled with a central processing unit (CPU, a processor), implements the basic computer model used since the 1940s.
In contemporary usage, memory usually refers to a form of semiconductor storage known as random access memory (RAM) and sometimes other forms of fast but temporary storage. Similarly, storage today more commonly refers to mass storage - optical discs, forms of magnetic storage like hard disks, and other types slower than RAM, but of a more permanent nature. Historically, memory and storage were respectively called primary storage and secondary storage.
The contemporary distinctions are helpful, because they are also fundamental to the architecture of computers in general. The distinctions also reflect an important and significant technical difference between memory and mass storage devices, which has been blurred by the historical usage of the term storage. Nevertheless, this article uses the traditional nomenclature.
Any data storage device; that records (stores) or retrieves (reads) information (data) from any medium, including the medium itself. A data storage device is a device for recording (storing) information (data). Recording can be done using virtually any form of energy, spanning from manual muscle power in handwriting, to acoustic vibrations in phonographic recording, to electromagnetic energy modulating magnetic tape and optical discs.
A storage device may hold information, process information, or both. A device that only holds information is a recording medium. Devices that process information (data storage equipment) may either access a separate portable (removable) recording medium or a permanent component to store and retrieve information.
C.OPERATING SYSTEM VS. COMPUTER SYSTEM
=
Operating system (commonly abbreviated to either OS or O/S) is an interface between hardware and user; it is responsible for the management and coordination of activities and the sharing of the resources of the computer. The operating system acts as a host for computing applications that are run on the machine. As a host, one of the purposes of an operating system is to handle the details of the operation of the hardware. This relieves application programs from having to manage these details and makes it easier to write applications. Almost all computers (including handheld computers, desktop computers, supercomputers, video game consoles) aswell as some robots, domestic appliances (dishwashers, washing machines), and portable media players use an operating system of some type. [1] Some of the oldest models may however use an embedded operating system, that may be contained on a compact disk or other data storage device.
Operating systems offer a number of services to application programs and users. Applications access these services through application programming interfaces (APIs) or system calls.
Operating system (commonly abbreviated to either OS or O/S) is an interface between hardware and user; it is responsible for the management and coordination of activities and the sharing of the resources of the computer. The operating system acts as a host for computing applications that are run on the machine. As a host, one of the purposes of an operating system is to handle the details of the operation of the hardware. This relieves application programs from having to manage these details and makes it easier to write applications. Almost all computers (including handheld computers, desktop computers, supercomputers, video game consoles) aswell as some robots, domestic appliances (dishwashers, washing machines), and portable media players use an operating system of some type. [1] Some of the oldest models may however use an embedded operating system, that may be contained on a compact disk or other data storage device.
Operating systems offer a number of services to application programs and users. Applications access these services through application programming interfaces (APIs) or system calls.
The Computer System Hardware category groups classes together that represent hardware related objects. Examples include input devices, hard disks, expansion cards, video devices, networking devices, and system power.
=
Subscribe to:
Posts (Atom)
