Today, Yahoo announced a new feature for YQL, and that is the Insert/Update/Delete feature. A spokesperson for Yahoo tells WebProNews this extends the platform by adding “write" capability to its capabilities, including YQL Open Data Tables and Execute."

If you’re interested in seeing some examples of how the new feature can be utilized, Yahoo has a blog post up about it that shows some things it can do.

One thing it can be used for is to bring some Twitter integration to your blog. "This enables YQL’s Open Data Tables to insert new Twitter status messages, not just list them; to add new comments to a blog, as well as read them; to store data in a remote database; to INSERT INTO internet," says Jonathan Trevor of the YQL Team.

"If you’ve developed some Open Data Tables already and the source supports some type of update, you might want to take this opportunity to go back and add the capability in," he says.

Documentation is available here for developers. To get a better understanding of what you can do, keep an eye on Yahoo’s developer blog. Besides the aforementioned post, Trevor says more examples and demos will be covered in the coming weeks.

Hence, most databases you may get from outside sources will probably be in the form of a MySQL injection script. This is fine if you use MySQL for your own website databases, but if you use Microsoft SQL Server the script will require a little editing before it will work.

The first thing you’ll need to do is remove any comment lines from the script. MySQL comment lines begin with a pound character (“#”) and MSSQL comment lines begin with a double dash (“–”), which makes them completely incompatible and will product a syntax error if you try to import a MySQL injection as-is into MSSQL Server. So to get started, open up Query Analyzer if you haven’t already (the easiest way to run scripts in MSSQL Server), load up the injection script you are working with, and remove any comment lines (look for the pound symbol). It is easier just to remove them than it is to try and convert them to propery MSSQL syntax, and they are just comment lines anyway so it won’t affect anything.

The bulk of your script will most likely be a series of INSERT statements, and these aren’t very different in MSSQL as compared to MySQL. However, your script may also include at the beginning a small section that creates the database table where the data will be inserted, and this CREATE TABLE statement is likely to be VERY different in MSSQL, depending on how complicated it is (there could be primary and secondary keys, constraints, even triggers — the more of these the more the syntax changes from MySQL to MSSQL). Since this is likely to give you the most trouble, it is recommended that you create the database tables manually in Enterprise Manager rather than trying to convert the syntax of the script snippet. Looking at the code, you should be able to easily identify the fields and their types (such as int, varchar, text, etc). Once you have the database table created in Enterprise Manager, delete the snippet of code from the injection script that deals with the creation of the table.

Now all that remains is to convert the INSERT statements to the proper syntax for MSSQL Server. There are a few different steps to accomplish this, but none of them are very complicated. The first difference in syntax between MySQL and MSSQL is that in MySQL, all statements must end with a semicolon (“;”). In MSSQL, this is a syntax error. The easiest way to remove these semicolons is to do a search and replace, and since the INSERT statements should be passing a series of values for each record of data, each line of the MySQL script will most likely end with a paranthesis and semicolon (“);”). So, do a search and replace and replace all instances of “);” with just the parenthesis “)”.

Another difference that you will have to correct for is that your MySQL injection script will most likely use an acute accent / reverse apostrophe (ANSI character 180) around the table name on each line. In MSSQL Server, you can encapsulate an object’s name (such as a table’s) with either square brackets (“[" and "]“) or nothing at all. However, you probably don’t want to do a blanket search-and-replace of the reverse apostrophe character, because that character might be used in the data of each record (especially if the data contains text, such as an article body). The easiest way to correct for this difference in syntax, then, is to do another search and replace, and replace all instances of the reverse apostrophe AND the table name, for example “`articles`” with just the table name “articles”.

Finally, there will also be numerous occurrences of apostrophes throughout the text fields of the data, and the apostrophe character is used to encapsulate strings in the script. In MySQL, the way to escape an apostrophe so that the script knows it is part of the text and not the end of the string, is to use a backslash followed by the apostrophe (“‘”). In a MSSQL Server script, the proper way to escape an apostrophe is to use a double apostrophe (“””). So, one more search and replace is called for — this time, replace all instances of ['] with [''] (double apostrophe, NOT an actual quotation mark).

Once these steps are all complete, you are ready to run the script! There shouldn’t be any other syntax changes you’ll have to make, but don’t worry if there are because when you execute the injection script it will tell you if there are any errors. If everything was corrected properly and there are no errors, you should get a series of “1 row(s) affected” responses — one for each INSERT statement in the script. If you want to verify that the proper number of records are in the database table, you can execute a “select count(*) from tablename” statement to count the rows of the table — it should match the number of lines in the injection script, give or take a few for blank lines, etc.

That’s it! Your options are now increased tremendously, because now you can use either MySQL or MSSQL injection scripts to import acquired databases into your database system. If you use MySQL as your dbms, you can do this process in reverse to convert a MSSQL injection script into a MySQL one. Either way, you now can import data using an injection script from either of the two most popular database management systems in the world. Now, where to obtain such databases or injection scripts is another question entirely, and beyond the scope of this article. Suffice it to say that there are numerous sources on the internet where you can purchase or acquire databases — a good one is www.WebContents.org. I think you will find that not only is it much easier to acquire content databases for your users than it is to build them from scratch, but it also is an easy way to add a lot of new, fresh content for your users with a minimal amount of time and effort. Using this method, you can get databases of articles, jokes, quotes, recipes, etc, and put them right on your website or any other database-integrated application, with very little work. Good luck!

Add to Del.icio.us | Digg | Reddit | Furl

Bookmark WebProNews:

This article was written by Lucas Green, a professional private web developer who lives off his internet income. To visit his website and learn more about how he is creating multiple streams of passive income using the internet, please visit www.lucasgreen.com !

They can evaluate data being added to a table for validation purposes, or can make changes in that or other fields depending on the value of that data. You can use them even to execute a separate stored procedure, or to roll back a data modification or an entire transaction.

In earlier versions of SQL Server, triggers were used to maintain referential integrity. In current versions, constraints and foreign keys are used to accomplish much of those tasks, but triggers are still used to accomplish more complex tasks than that are available to the built in newer tools, such as complex column constraints, evaluation of tables in other databases, complicated defaults, or cascading routines involving multiple changes in multiple tables.

Triggers are created in the Enterprise Manager, or in the Query Analyzer through the object browser. There are also templates for triggers in the Query Analyzer (Edit|Insert Trigger). Triggers can be created with the following syntax:

CREATE TRIGGER trigger_name
ON { table | view }
[ WITH ENCRYPTION ]
{
      { { FOR | AFTER | INSTEAD OF } { [ INSERT ] [ , ] [ UPDATE ] }
            [ WITH APPEND ]
            [ NOT FOR REPLICATION ]
            AS
            [ { IF UPDATE ( column )
              [ { AND | OR } UPDATE ( column ) ]
                [ ... n ]
            | IF ( COLUMNS_UPDATED ( ) { bitwise_operator } updated_bitmask )
                { comparison_operator } column_bitmask [ ... n ]
            } ]
            sql_statement [ ... n ]
      }
}

There are two types of triggers: AFTER and INSTEAD OF. After triggers AFTER TRIGGERS fire after the data is changed, either by insert, delete, or update. If the data is inappropriate, as defined in the trigger, the modification can be rolled back to where it was before the data was modified. After triggers AFTER TRIGGERS cannot be placed on views, and cannot be used on more than one table. Also, the text, ntext, and image columns cannot be referenced in an after trigger. AFTER TRIGGERS.

After triggers AFTER TRIGGERS can be nested to 32 levels deep, and can be called recursively, again to 32 levels.

Instead of INSTEAD OF triggers make the validation before the modification. However, Instead of INSTEAD OF triggers CAN can be used on views. They do not allow recursion, and you can only have one Instead of INSTEAD OF trigger per table. And you cannot use an Instead of INSTEAD OF trigger with a cascade.

Resources

This resource discusses about constraints and triggers in detail.

This resource is useful in understanding the workings of triggers in detail.

Tag:

Add to Del.icio.us | Digg | Reddit | Furl

Bookmark WebProNews:

Metro NY / NJ SQL Server Consultants
We specialize is custom database software. Call us for a free consultation (973) 635 0080 or email us at paladn.com

Chris Kemp is a well known author in the field of Information Technology. His articles are very popular and well known in the various article banks across internet. His popular articles are about SQL Server, Database Design, IT Consulting and Software Development.

chriskemp@webpopularity.org

From a bit to a huge image and binary storage types, the allocation is supposed to help the user conform to the data required, and help the engine allocate space and processing speed efficiently.

Built-in data types

SQL Server 2000 recognizes the following built in data types:

Data Types
Description

bigint
Integer data from -2^63 through 2^63-1

int
Integer data from -2^31 through 2^31 – 1

smallint
Integer data from -2^15 through 2^15 – 1

tinyint
Integer data from 0 through 255

bit
Integer data with either a 1 or 0 value

decimal
Fixed precision and scale numeric data from -10^38 +1 through 10^38 -1

numeric
Fixed precision and scale numeric data from -10^38 +1 through 10^38 -1

money
Monetary data values from -2^63 through 2^63 – 1

smallmoney
Monetary data values from -214,748.3648 through +214,748.3647

float
Floating precision number data from -1.79E + 308 through 1.79E + 308

real
Floating precision number data from -3.40E + 38 through 3.40E + 38

datetime
Date and time data from January 1, 1753, through December 31, 9999, with an accuracy of 3.33 milliseconds

smalldatetime
Date and time data from January 1, 1900, through June 6, 2079, with an accuracy of one minute

char
Fixed-length character data with a maximum length of 8,000 characters

varchar
Variable-length data with a maximum of 8,000 characters

text
Variable-length data with a maximum length of 2^31 – 1 characters

nchar
Fixed-length Unicode data with a maximum length of 4,000 characters

nvarchar
Variable-length Unicode data with a maximum length of 4,000 characters

ntext
Variable-length Unicode data with a maximum length of 2^30 – 1 characters

binary
Fixed-length binary data with a maximum length of 8,000 bytes

varbinary
Variable-length binary data with a maximum length of 8,000 bytes

image
Variable-length binary data with a maximum length of 2^31 – 1 bytes

cursor
A reference to a cursor

sql_variant
A data type that stores values of various data types, except text, ntext, timestamp, and sql_variant

table
A special data type used to store a result set for later processing

timestamp
A database-wide unique number that gets updated every time a row gets updated

uniqueidentifier
A globally unique identifier

Bigint, sql_variant, and table are new to SQL Server 2000

User-defined data types

You can make user-defined data types too, which sometimes can be more descriptive of the value types held in the object. This may make it easier for the programmer to document and work with the data. These data types are based on the built in types, and can be outfitted with preprogrammed defaults, checks, constraints, etc. . To create a user-defined data type, use

sp_addtype datatypename, basedatatype, NULL’/'NOT NULL’

How to choose the appropriate data type

SQL Server stores data in data pages that are 8Kb (8192 bytes) in size. The system uses some of that s Sometimes, the system uses only 8060 bytes are availableto that are available to store user’s data. Consider the size of a row of data in your tables. If the rows are large, make sure that multiples of the fit conveniently on a data page so that page space is not wasted. This is cut down on disk paging overhead when accessing the data. You want to maximize the number of rows of data which that will fit on a page. This can be accomplished both by splitting the tables, and by choosing the smallest data type which that will accommodate your data. .

In you are using integer data, data; consider that the tinyint datatype will accommodate data which that will fit into one byte of storage. So if the range of all of the data in your field (or variable) is between 0 and 255, use the tinyint datatype. If the range is between -32,768 and 32,767, use the smallint data type. And if If you need to store integer data from -2,147,483,648 through 2,147,483,647, use int data type.

Similarly with smallmoney. If smallmoney. if your value range is between -214748.3648 and 214,748.3647, use the smallmoney datatype.

Use smalldatetime data type instead of datetime data type, if you need to store the date and time data from January 1, 1900 through June 6, 2079, with accuracy to the minute.

Prefer varchar.nvarchar to text/ntext whenever possible because the text and image fields are stored separately, which produces additional paging. And prefer char/varchar to nchar/nvarchar data types because the n types require twice as much storage space. The n types are used primarily for unicode data.

Resources

Tutorial: SQL 7 & Database Files
This is a useful tutorial on SQL & and database Files.

Information: Complete information on SQL
This resource provides complete information on SQL.

Tag:

Add to Del.icio.us | Digg | Reddit | Furl

Bookmark WebProNews:

Metro NY / NJ SQL Server Consultants
We specialize is custom database software. Call us for a free consultation (973) 635 0080 or email us at paladn.com

Chris Kemp is a well known author in the field of Information Technology. His articles are very popular and well known in the various article banks across internet. His popular articles are about SQL Server, Database Design, IT Consulting and Software Development.

chriskemp@webpopularity.org

1. Cross Site Scripting (21.5%)

2. SQL Injection (14%)

3. PHP includes (9.5%)

4. Buffer overflows (7.9%)

Mike Sutton wanted to know just how prevalent are SQL Injection Vulnerabilities? So he ran a little test, and found that out of 1000 web sites 11.3% of them were vulnerable!

I also heard this from Mike Andrews in his How to Break Web Software talk. He says that the number of buffer overflow vulnerabilities have been going down over the years as more people are aware of them, and there are lots of automated tools for finding them. But the number of web application vulnerabilities has been sky rocketing.

Buffer Overflows were first talked about in the 1970′s by the NSA, and they are still somewhat of a problem – do you think we will still be talking about Cross Site Scripting and SQL Injection in 30 years?

Comments

Related Entries

How to Break Web Software – April 21, 2006

Top 20 Internet Security Vulnerabilities of 2005 – November 23, 2005

MySpace Hacked with CSRF and XSS – October 13, 2005

Detecting SQL Injection with ScriptProtect – May 18, 2005

ScriptProtect in ColdFusion MX 7 not a catch all – May 17, 2005

Digg | Reddit | Furl

Bookmark WebProNews:

*Originally published at Pete Freitag’s Homepage.

Pete Freitag (http://www.petefreitag.com/) is a software engineer, and
web developer located in central new york. Pete specializes in the
HTTP protocol, web services, xml, java, and coldfusion. In 2003 Pete
published the ColdFusion MX Developers Cookbook with SAMs Publishing.

Pete owns a Firm called Foundeo (http://foundeo.com/) that specializes
in Web Consulting, and Products for Web Developers.

It can be installed as a storage engine type on MySQL, and from what I hear can beat the pants off of MySQL’s built-in full text search in some cases.

From the web site:

Generally, it’s a standalone search engine, meant to provide fast, size-efficient and relevant fulltext search functions to other applications. Sphinx was specially designed to integrate well with SQL databases and scripting languages. Currently built-in data sources support fetching data either via direct connection to MySQL, or from an XML pipe.

Here are some of the features:

• high indexing speed (upto 10 MB/sec on modern CPUs)
• high search speed (avg query is under 0.1 sec on 2-4 GB text collections)
• high scalability (upto 100 GB of text, upto 100 M documents on a single CPU)
• supports distributed searching (since v.0.9.6)
• supports MySQL natively (MyISAM and InnoDB tables are both supported)
• supports phrase searching
• supports phrase proximity ranking, providing good relevance
• supports English and Russian stemming
• supports any number of document fields (weights can be changed on the fly)
• supports document groups
• supports stopwords
• supports different search modes (“match all”, “match phrase” and “match any”)
• generic XML interface which grealy simplifies custom integration

Related Entries

• MySQL FULLTEXT Indexing and Searching – September 29, 2005
• Updated SQL Reserved Words Checker – March 28, 2006
• SQL to Select a random row from a database table – September 14, 2005
• Insert Delayed with MySQL – August 2, 2005
• Multiple Inserts with MySQL – June 10, 2005

Comments

*Originally published at Pete Freitag’s Homepage

Tag:

Add to Del.icio.us | Digg | Reddit | Furl

Bookmark WebProNews:

Pete Freitag (http://www.petefreitag.com/) is a software engineer, and
web developer located in central new york. Pete specializes in the
HTTP protocol, web services, xml, java, and coldfusion. In 2003 Pete
published the ColdFusion MX Developers Cookbook with SAMs Publishing.

Pete owns a Firm called Foundeo (http://foundeo.com/) that specializes
in Web Consulting, and Products for Web Developers.

More are more developers are struggling to find the right answer, but the answer really depends on the developer’s individual needs.

For classic SQL tasks, the good old TSQL is recommended. On the other hand, CLR works best for calculations, parsing, image processing and other tasks that deal with a very limited amount of data.

We performed an experiment that defies the common perception that calculation tasks run several times faster when implemented in CLR form. For this experiment, we utilized a computer with Pentium 4 2.4GHZ processor and 1 Gb of RAM.

We created a very simple user defined function on T-SQL that adds two numbers. The function is found below:

CREATE FUNCTION FuncSum(@n1 INT, @n2 INT) RETURNS INT AS BEGIN RETURN @n1 + @n2 END

Then, we rewrote the same function using CLR this time. This looks a little bit more complicated.

using System; using Microsoft.SqlServer.Server;

public class TestProcedures { [Microsoft.SqlServer.Server.SqlFunction( IsDeterministic = true, DataAccess = DataAccessKind.Read )] [CLSCompliant( false )] public static int FuncSum_CLR(int n1, int n2) { return n1 + n2; } }

After which, we loaded them into our database:

CREATE ASSEMBLY SQL2005_Assembly FROM 'C:\Documents and Settings\User\My Documents\Visual Studio 2005\Projects\SQL2005_Assembly\bin\Release\SQL2005_Assembly.dll' WITH PERMISSION_SET = UNSAFE

CREATE FUNCTION FuncSum_CLR ( @n1 int, @n2 int ) RETURNS int AS EXTERNAL NAME SQL2005_Assembly.TestProcedures.FuncSum_CLR

We then ran the TSQL and CLR function 100,000 times over and compared the result:

CREATE PROCEDURE TestFuncSum(_CLR) AS BEGIN DECLARE @t datetime SET @t = getdate() DECLARE @n INT DECLARE @i INT SET @i = 0 WHILE (@i < 100000) BEGIN EXEC @n = FuncSum(_CLR) 1,1 SET @i = @i + 1 END SELECT datediff(ms, @t, getdate()) END

The results were revealing:

* TSQL: 2000ms * CLR: 6300ms

The experiment proved that CLR was running more than three times slower on a mere calculation task. Here's the explanation:

Obviously, it takes time for the SQL server to switch the context from the kernel to the CLR (.Net framework). This time in that experiment can be estimated using formula (6300-2000)/100000 = 0.042ms. It is almost nothing in comparison with other executions, remember, even SQL profiler does not detect time periods less then 13-16ms.

However, it might be important if you are using CLR functions in WHERE conditions or as a parameters to the aggregation functions, which are called thousands of times.

This overhead is the same for TSQL and CLR procedures.

The Mystery of 'Return'. Why SQL2005 is slower then SQL2000.

We continued on with our experiments that call almost empty procedures thousands of times over. The results are once again revealing.

Experiments are again done on a computer with Pentium 4 2.4GHz processor and 1Gb of RAM.

We created three procedures that do nothing. You read right, they do absolutely nothing.

CREATE PROCEDURE Proc_Return1 AS RETURN GO

CREATE PROCEDURE Proc_Return3 AS RETURN 1 GO

In the second procedure, there were unreachable statements after the RETURN. They were not an error. We too thought that there is no difference, but we then called all three procedures 100K times:

CREATE PROCEDURE TestProc_Return1 AS BEGIN DECLARE @t datetime SET @t = getdate() DECLARE @i INT SET @i = 0 WHILE (@i < 100000) BEGIN EXEC Proc_Return(1/2/3) SET @i = @i + 1 END SELECT datediff(ms, @t, getdate()) END GO

And we got the following results:

SQL 2000 SQL 2005 EXEC TestProc_Return1 2120ms 1850 EXEC TestProc_Return2 1200ms 1850 EXEC TestProc_Return3 1300ms 1850

What do these results mean?

* Mysteriously, unreachable code after the RETURN helps it running faster. Only God and Microsoft know why, I don't have any logical explanation. It is believed that SET statements are more useful then the others. You can continue my experiments with the different statements and share the result.

* RETURN 1 also helps, and is twice faster than RETURN

* Finally, this mysterious behavior is fixed on SQL 2005... it is always running slow...

Now that is more important. Note: this is actually a case where SQL 2005 is running almost 2 times slower then SQL 2000 on the same code. And that can hurt on the production! Is it the only case? No, we will continue the investigation.

Tag:

Add to Del.icio.us | Digg | Yahoo! My Web | Furl

Bookmark WebProNews:

http://www.lakesidesql.com/

Kritzer’s list began with a preface on why she tries to live by the eight SQL rules in her post about best practices:

Kritzer started the list by suggesting database developers always use explicit joins. “If I mean INNER JOIN, then I use INNER JOIN. No use of just plain “JOIN”. Never, ever, ever use a comma join – I consider that a mistake,” she wrote.

One person asked about that practice in a comment about the post. Peter Zaitsev of the MySQL Performance Blog said this:

Kritzer agreed in her response that the use of explicit joins is definitely syntax. “I feel that specifying INNER vs. LEFT or RIGHT or CROSS helps them understand that they’re not saying “I want you to join the tables,” ie, take an action, they’re saying, “I want the result if you join the tables this way,” ie, “this is what I want back.”

Database pros should not be afraid of JOINS. If good indexing has been used for the database, Krtizer said JOINS are not necessarily resource-intensive. And when a correlated subquery can be replaced with a JOIN, it should be replaced.

Developers should also always define field names. “No using SELECT * or INSERT INTO table VALUES. It’s a pain,” she wrote. For reporting, always use the timestamp from the database server, in case those of web servers are different.

Reporting will go more smoothly if one stores IPs as integers with INET_ATON and retrieves them with INET_NTOA, Kritzer also wrote. On the topic of reporting, she considered the impact of network traffic and made this best practice suggestion:

“Running a query in a loop is usually a bad idea,” Kritzer said of those. “Consider building a query string using UNION and executing it at the end of the loop, so you can execute multiple queries with only one trip across the network to the database.”

—

Add to Del.icio.us | Digg | Yahoo! My Web | Furl

Bookmark WebProNews:

David Utter is a staff writer for WebProNews covering technology and business.

In present, a wide range of IT companies are striving to provide business owners with better application management and new, state-of-the-art development solutions and tools, vital for increasing productivity and facilitating process development for any business. In order to improve the overall performance of commonly used application servers, and to enhance the efficiency of specific application programs, more and more IT companies are currently aiming to develop new, competitive software programs that support popular, commonly used databases. Such software products offer an extended set of features that help businesses implement better management and development solutions and also considerably reduce the time, effort and costs of process development.

Most software products implement support for MySQL databases, providing users with a complete set of improved administration and development solutions. Enhancing and correcting the features provided by the popular MySQL Manager application, MySQL Turbo Manager is by far the best software solution for MySQL database management, administration and development in present. The small MySQL Manager application included by Mac OS X Server provides users with a GUI interface for a set of basic actions. However, the standard MySQL Manager application can’t effectively meet today’s requirements, users needing more powerful and complex applications for creating, managing and interacting with various databases.

MySQL Turbo Manager accounts for the minuses of the regular MySQL Manager application, also implementing new reliable features that account for all the issues of an effective process development. MySQL Turbo Manager is nowadays considered to be a very powerful and easy to use administration tool, successfully meeting the requirements of a wide range of businesses. MySQL Turbo Manager is an effective MySQL Front End, a Graphical User Interface (GUI) Server for MySQL, renowned as the most reliable administration tool in present.

Similar to MySQL Turbo Manager, Dream Coder is a very effective Front End for Oracle database, regarded as a powerful PL/SQL IDE by a large number of businesses from various fields of activity. Dream Coder for Oracle is undoubtedly the most effective PL/SQL IDE (Integrated Development Environment), greatly reducing the time and costs required by the development process. With the help of Dream Coder for Oracle databases, PL/SQL developers can now browse trough a more intuitive and user-friendly GUI and perform various tasks with a minimal investment of time and effort.

Dream Coder for Oracle is a complete software product, providing PL/SQL developers with an extensive set of features such as building and executing queries, creating and executing scripts, creating and modifying database objects, user session monitoring, database monitoring and many more. Along with MySQL Turbo Manager, Dream Coder for Oracle is nowadays a highly requested software product, greatly facilitating process development and improving productivity with a small investment of time and effort.

Tag:

Add to Del.icio.us | Digg | Yahoo! My Web | Furl

Bookmark WebProNews:

So if you want to find out more information about MySQL Front End or about PL/SQL Developer, or even about PL/SQL IDE please click these links.

The more the number of users supported by the application the more will be the load on the server to act on their requests. Especially in cases of a web application, the location of the server plays an important role because unlike your inhouse application a web application may have users from all around the globe. Managing data for such huge number of users on one centralized server become very difficult. You may face the following problems.

* Performance: since there are huge number of users accessing your database it may slow down in executing requests.

* Consistency: incase the server goes down, people accessing your service will remain temporarily disconnected until they server is up and running.

SQL Replication is the answer to this problem. SQL Replication can be defined as a process of sharing data across different networks or different locations. It creates copies of database and these copies are shared with among different network and locations. The users accessing that network will make changes to this copy of data which will be later synchronized with the original database. Advantages of SQL Replication over a centralized server approach are:

* It provides more consistency for user who can now access their local copy of data even if the original server is temporarily not working.

* SQL Replication can be a sort of data recovery tool if you happen to loose your data by theft, fire or other natural disasters. You still have a copy of your database which will keep your service running.

* By replicating data on network servers the load on the central server is decreased which reduces network traffic.

* It provides excellent synchronization technique that synchronizes all the replication data with the original database.

Tag:

Add to Del.icio.us | Digg | Yahoo! My Web | Furl

Bookmark WebProNews:

This article is published by content writer of Search Influence Inc, US based SEO company on behalf of http://www.globaldatavault.com. For more information about Global Data Vault can be retrieved by visiting