Topic: We all had the unfortunate experience of seeing how computers can, at times, make life's journey about more difficult. This is especially true in knowledge-centric workplaces. Describe an examp

Friends Post 01

Computers can make life easy to store, retrieve, update files in hard disks during the early days of invention of computers. Once Internet started exploding, the data usage and storage capacity has increased. Ideally, later the data is stored in cloud and certain databases to allow the ease of access to files and data wherever there is internet. With the growing changes, there are different databases used based on various factors like functionality, cost, support, speed and maintainability. However, a poorly designed database designs can lead to slower rate of retrieving the data.

There are many databases which are designed poorly and perform poorly upon fetching data using a query or updating the data. Every database should have unique key or identifier to retrieve only that object. Each value in database should have char length, i.e. character limit. If there is any date, the date should be in standard format and should follow UTC time zone because, different locations have different time zone. Date should be always stored in date-time format, not as a varchar. Design should be made in such a way that, if there is no value, it shouldn’t be null updated as string but null by default. Database should be free from duplicates as this hampers the unique key identifier. There shouldn’t be two rows with same keys. All the data should be consistent among all the objects, for example, if phone numbers have spaces with and some phone numbers don’t have spaces, it is an inconsistent way of storing the data. If the data set is having no values, it should be either empty string or NULL. If there is no primary key in the table, the performance will slow down while retrieving the data. All the CRUD operations such as create, read, update and delete will be impacted. If the database doesn’t have an index in each data set, ideally, it is not possible to sort. Sometimes by updating a single entity in User Interface, will update multiple entities and columns in database.

Next thing we need to consider is the data migration. In case, the data already exists somewhere in different database, it needs to be migrated properly and database needs to be structured carefully. This can be difficult task when data is incomplete or inconsistent. There are numerous techniques and ways to migrate the absent data. It will depend on the technique while migrating. Generally, ETL process is used for data migration. This process reduces lot of ways one can migrate the code.

Another difficult task for the developers to take care is the to reduce the time of queries. Ideally, the database should have good design, database should not ignore normalization. Good database should have documentation and support. Every database should have unique key for each object. For data integrity, it must use SQL facilities and should use standard stored procedures to access data. Good database should prevent generic objects getting stored and it should throw an exception and finally should be testable.

References:

1.     Batini, C., Ceri, S., & Navathe, S. B. (1992). Conceptual database design: an Entity-relationship approach (Vol. 116). Redwood City, CA: Benjamin/Cummings.

2.     Kahn, B. K. (1976, June). A method for describing information required by the database design process. In Proceedings of the 1976 ACM SIGMOD international conference on Management of data (pp. 53-64). ACM.



Friend Post 02:


companies acquire information from their clients to do various operations at the facts, to offer higher service to its customers. They store the facts gathered within the database of the enterprise. essentially, a house plan or outline is needed for the improvement of the house. In every business undertaking, the foundation is the database if the need for the venture isn't always mapped and assembly the database with the aid of gaining time. in the structure of a database, and numerous progressions must be located by gaining the time toward the starting where the complete assignment has a giant impact with the goal that the expected chance is amplified. For the maximum part, through watching for the finishing matters, the duration of suitable arranging is not noted. due to the absence of valid arranging and structuring certainly, the troubles are added up in a particular bearing and with the quality feasible techniques. these days the generation is converting so swiftly that the new software program is being developed, so it is very critical to have an updated database to be successful in this competitive international.

the principle assignment with the database is it is not easy to use, it is a bit puzzling. It has many sets of capabilities for information garage like facts, tables, perspectives, columns, and constraints which makes it very difficult to use. (Martinez, n.d.) once the developer is aware of the way to use some of these features in a database, then it will be very clean for them to apply and actually they'll locate many new solutions to enhance it. The challenges of the database are: (Martinez, n.d.).no longer knowing why the information is wanted. (Martinez, n.d.).

We typically save records so that we can retrieve it and carry out operations on the statistics. So, the developer needs to realize what the factors that might be needed to retrieve later and the way to retrieve and wherein manner will they be wanted.

Bad Normalization (Martinez, n.d.)exceptional records base developers might have used the equal ideas of normalization, but nevertheless, they may have one-of-a-kind patterns of statistics entry. The layouts can be different. So, it must be normalized to its 0.33 shape, so that everyone can comply with the identical entity entry.

records Redundancy (Martinez, n.d.)once in a while, in business, even as entering data, the information might be had to enter a range of times which reasons redundancy. The database is commonly used to reduce redundancy, however in these cases, it is again becoming an undertaking, so if the normalization guidelines are observed well and diligently, then facts redundancy can be decreased.

Bad integrity for Reference is proper equipment for a database to maintain its integrity and to have the pleasant first-rate of information. If there are no references, and information is completely dependable on common sense, then there might be mistakes and mistakes due to human interference.

Neglecting the capabilities of the Database engine (systems., 2007)there are many in constructed feature in the database for you to save statistics and do capabilities of records without any error, in which in it could be assured that records entered is safe, secure, reliable and without difficulty retrieved. The database is all about a whole lot of software which makes paintings easy however the developers need to have proper knowledge on where to use the features and a way to use the capabilities.

References:

1. Blaha, M. R. (2001). A managers guide to database technology: Building and purchasing better applications. Upper Saddle River, NJ: Prentice Hall.

2. Swami (1995), Dynamic questions for data investigation: execution and assessment. A visual way to deal with perusing in a database domain. An Introduction to the Human Applications Standard Computer Interface. IEEE Database Engineering.


Friend post 03

EFFECTS OF POOR DATABASE


Actually Database refers to a collection of electronic records that could be processed to produce useful information, the data is accessed, modified, managed, controlled and organized to perform various data-processing operations. The data is often indexed across rows, columns and tables that make workload processing and data querying efficient.

There are different types of databases: Object-oriented, Relational, Distributed, Hierarchical, Network and others. In enterprise applications, databases involve mission-critical, security-sensitive and compliance-focused record items that have complicated logical relationships with other datasets and grow exponentially over time as the user base increases. As a result, these organizations need technology solutions to maintain, secure, manage and process the data stored in databases. This is where Database Management System comes into play.

Info is of any size and complexness. The data is also generated and maintained manually or it's going to be computerized. For instance, if we go to the bank to deposit or withdraw funds, if we make a hotel or airline reservation, if we access a computerized library catalog to search for a listing item, or if we purchase something online such as a book, toy, or computer chances are that our activities will involve someone or some computer program accessing database. Even getting things at a grocery usually mechanically updates the info that holds the inventory of grocery things (C Coronel, S Morris, 2016).

 

 

There are many advantages and also disadvantages of using database.

Advantages
• Reduced data redundancy
• Reduced updating errors and increased consistency

• Larger information integrity and independence from applications programs

• Improved information access to users through use of host and question languages

• Improved data security
• Reduced data entry, storage, and retrieval costs
• Facilitated development of new applications program

Disadvantages

• Info systems are advanced, difficult, and time-consuming to design

• Substantial hardware and software start-up costs

• Harm to info affects nearly all applications programs

• Intensive conversion prices in moving kind a file-based system to a info system

• Initial coaching needed for all programmers and users

Implementation of Database:

Development, deployment and subsequent performance in production are destined to give little trouble if the database design is done in the right way. If a database that is correctly implemented “just works” However, during database design, a small number of mistakes can cause subsequent misery to the DBAs, managers, and developers (H Garcia-Molina, JD Ullman, J Widom, 2000).

For instance the poorly implemented database that I have encountered in liven compasses order management system database in an organization Myntra that related to sales. Often, order management system database requires a client to be assigned one or more address, a default sales person who will connect the organization and the client, and one or more phone contacts Again, this type of database contain particular shipment information such as dates, number of boxes to be shipped, bill of lading number. However, customers of organization Myntra were poorly served such that contacts and billing address were mixed up. The immediate impact of this was that wrong shipment was done often. This poor implementation was because of irregular reviewing and checking of the database. This caused the codes in the system (representing the information of the clients) to migrate unnecessarily, mixing up the information. A reiterate that irregular reviewing and checking of the database results in incorrect data configuration and the corresponding implementations. This problem can be corrected by constantly reviewing the process to ensure that the codes are put in the right place. This strategy is important in identifying possible conflicts resulting during the configuration of the codes.

References

Coronel, C., & Morris, S. (2016). Database systems: design, implementation, & management. Cengage Learning.

DeWitt, D. J., Katz, R. H., Olken, F., Shapiro, L. D., Stonebraker, M. R., & Wood, D. A. (1984). Implementation techniques for main memory database systems (Vol. 14, No. 2, pp. 1-8). ACM.

Garcia-Molina, H., Ullman, J. D., & Widom, J. (2000). Database system implementation (Vol. 672). Upper Saddle River, NJ:: Prentice Hall.


Friend post 04

A case of an ineffectively executed database that I have experienced is the place an originator was building a database for a flower vendor, and he utilized an alternate name from that which the flower vendor employments. This issue is alluded to as poor naming guidelines. Even though names are an individual decision, they are thought to be an extremely vital line of documentation in any application. Utilizing diverse names to portray a similar thing by the originator and the flower vendor can botch things up because it would realize challenges in the recognizable proof of the item at the season of offer. There is along these lines an extraordinary requirement for consistency to such an extent that the names picked are not utilized for the recognizable proof of the question right now however to help the other future software engineers and the clients to effortlessly and rapidly get a reasonable comprehension of how the different parts of the database expected to be utilized and the information that is put away in it.


The creator of a database ought to guarantee that the future clients of the outline don't require swimming through pages of different archives with the goal that they can get the importance of the different names that have been utilized as a part of the database. The designers of a site ought to be in a situation to establish that the name of a specific table is a table name by the setting in the device or code and guarantee that they present to the clients straightforward, graphic and clear names. Notwithstanding guaranteeing consistency in the names utilized, the engineers ought to likewise maintain a strategic distance from the example of utilizing spaces and cited identifiers in the names of the items as an answer for the minimization of the occurrences of poor naming guidelines. The engineers ought to stay away from names that have spaces in the middle of which would require the clients to incorporate the spaces and the identifiers in their codes since it's pointless


Example


The best illustration I can say here is the database of distinguishing proof cards which is being kept up in IT organization, where it will have the points of interest of people with Name, age, Address, DOB, Phone number, email id alongside their fingerprints. This is one of the greatest biometrics database on the planet. Everybody will have a one of a kind distinguishing proof number and this can be utilized as an administration approved recognizable proof card for different purposes.


There are a few issues related with this biometrics database. Amid its expressing stage the undertaking was carried on an expansive scale. The information being gathered is finished by typical students who doesn't have any great hands on involvement. Number of errors are being accounted for disgraceful section of information which brought about unstructured development of information.


Issue:


The principle issue related with this database is occurred at a ground level where the students are neglected to enter the information into database legitimately. This has raised worried about disseminating the card with false/crisscrossing points of interest on it.


Arrangement:


Procuring a very much experienced person who has great learning about what he is doing (entering the information in to framework on application is the best cure we can give here for this situation. As it is going on at the ground level which is the most vital part in building up a decent and stable database.


It is said this is the greatest ever biometrics database being based on the earth. Its assembled extreme and kept up well without being slipping on to the hands of individuals who can abuse the information. The administration of India as of late has offered opportunity to refresh their subtle elements through government offices if the points of interest on the card are not right or confusing.


References


Natan, R. (2005). Implementing database security and auditing : a guide for DBAs, information security administrators and auditors. Burlington, MA: Elsevier Digital Press.