Once you've built several MySQL databases, you'll learn some shortcuts to database design. Why stop there? Take this trick a step further and put together a generic database with a set of empty, standard tables. With a well-designed MySQL template, you can quickly assemble the basics of any database as needed. A template also allows you to focus on the more interesting aspects of a database project.
A step-by-step must read article on SQL 2005 Reporting Services which creates a report and hosts it on an intranet server.
In this article I will cover the basics of migrating an application from an Access or SQL Server database to MySQL. We'll start with various reasons why you should (or should not) migrate your existing Access or SQL Server database to MySQL, then cover the planning stages of an application migration. Next we will look at the tools and methods for migrating your actual data from Access/MSSQL to MySQL, followed by some general guidelines for modifying your client application from a Microsoft database to MySQL. Finally, we'll look at some considerations to make when deploying your new MySQL database and application.
With many database vendor products in the market and data intensive applications using them, it is often required to port the application to use the data or, migrate the data so that the application can use it. Migration of data is therefore one of the realities of the IT Industry. Some of the author's previous articles on migration can be found at the link.
MobiLink is a technology that can help multiple databases synchronized, a key requirement for mobile access to data. The article shows you how to create a model that can be deployed to access data on a SLQ 2005 Server remotely with a SQL Anyhwhere database. A forth coming article descibes the deployment details.
Unlike most of the other projects in this book, NoSQL is not a tool, but an ecosystem composed of several complimentary and competing tools. The tools branded with the NoSQL monicker provide an alternative to SQL-based relational database systems for storing data. To understand NoSQL, we have to understand the space of available tools, and see how the design of each one explores the space of data storage possibilities.
This hands-on tutorial should help you in understanding the interface available for querying MS SQL Server 2005 databases. Some of the major features will be discussed as related to their use rather than going into a lot of details. Querying the database is one of the most basic activities that is routinely and frequently performed.
A function is a special type of command word in the SQL99 command set. In effect, functions are one-word commands that return a single value. The value of a function can be determined by input parameters, as with a function that averages a list of database values. But many functions do not use any type of input parameter.
Even if the vast number of end users leads to high calculation loads outside the database, you can generally throw hardware at the application load (the load outside the database, that is), hanging as many application servers as necessary off the single central database.
This article by Jayaram Krishnswamy shows how you can develop a VB.NET 2.0 application using the integration features provided by the SQL Anywhere database. The SQL Anywhere tools are directly accessible without going out of the Visual Studio 2.O IDE. The article describes a window application with two examples developed with this easy to use integration interface.
FileMaker 9 opens up ODBC data in a revolutionary way, via the new feature External SQL Data Source. You can work with external data in your FileMaker Pro solutions as if it is FileMaker Pro data.