Showing entries 11 to 20 of 65
« 10 Newer Entries | 10 Older Entries »
Displaying posts with tag: maxdb (reset)
MaxDB series: news but no series posting

Dear MySQL users, MaxDB users and friends,

we have two news for you. The bad one: no MaxDB series posting this week. The good one: german language MaxDB web seminar tomorrow!

My last week has been dominated by preparing the upcoming MaxDB web seminar on MaxDB performance tuning. The web seminar will be held in german tomorrow Thursday, 21.04.2006 at 10 CEST (MEZ). You can still register for the seminar at http://www.mysql.de/news-and-events/web-seminars/maxdb-performance.php. Don’t expect too much from the 45-minute talk. In 45-minutes one can’t do much more than talk about the very basics and try to give you an overview on the topic. Due to the web seminar and other duties we did not make it to write the next MaxDB series posting on transactions.

We have more good news for you. My co-worker C.J. Collier is …

[Read more]
MaxDB series: ?just SQL

Dear MySQL users, MaxDB users and friends,

The previous “please wait” posting was caused by a new guideline on series postings. The new guideline says that postings must be written one week before they get published. The week between the writing and the publication is used for corrections. I’m writing these lines on April, 4th but the article won’t be published before Wednesday April, 12th. We hope that in the time between writing and publishing we can catch most of the Gotchas to further improve the quality of the series. However, this series will continue to be more like a collection of blog postings than a book, a magazine article or any other “official documentation”. We try to do our best, but unfortunately we cannot apply the same amount of quality assurance and proof-reading to the MaxDB series that we do for magazine articles, official documentation or official class materials.

In this issue

In …

[Read more]
MaxDB series: …just SQL

Dear MySQL users, MaxDB users and friends,

The previous “please wait” posting was caused by a new guideline on series postings. The new guideline says that postings must be written one week before they get published. The week between the writing and the publication is used for corrections. I’m writing these lines on April, 4th but the article won’t be published before Wednesday April, 12th. We hope that in the time between writing and publishing we can catch most of the Gotchas to further improve the quality of the series. However, this series will continue to be more like a collection of blog postings than a book, a magazine article or any other “official documentation”. We try to do our best, but unfortunately we cannot apply the same amount of quality assurance and proof-reading to the MaxDB series that we do for magazine articles, official documentation or official class materials.

In this issue

In …

[Read more]
MySQL AB :: The MaxDB series on PlanetMySQL.

We’ve published the first few episodes of the weekly MaxDB series in .pdf form. Please take a look and let us know what you think!

MySQL AB :: The MaxDB series on PlanetMySQL.

© cjcollier for C.J.'s WordPress of studlyness, 2006. | Permalink | No comment

Add to del.icio.us

Search blogs linking this post with Technorati

Want more on these topics ? Browse the …

[Read more]
Useful MaxDB commands

To find a list of tables in a schema:

$ sqlcli -u TEST,TEST -d SYNCMANA "SELECT * FROM TABLES WHERE SCHEMANAME = 'TEST'"

To find a list of triggers on a table:

$ sqlcli -u DBSERVICE,SECRET -d SYNCMANA "SELECT * FROM TRIGGERS WHERE TABLENAME = 'T'"

To describe a table’s structure:

$ cat me && echo "-----" && 
   loadercli -d SYNCMANA -u TEST,TEST -b ./me && echo "-----" && 
   cat tabledef.txt
dataextract for dataload table T
outstream file 'tabledef.txt'
outstream file 'idontcare'

-----
Loader protocol: '/home/cjcollier/.sdb/loader/log/loader.prt'
Loader packages: '/home/cjcollier/sdb/loader/packages'

User TEST connected to database SYNCMANA schema TEST on local host.
dataextract for dataload table T
outstream file 'tabledef.txt'
outstream file 'idontcare'
Successfully executed

-----
//
CREATE TABLE "T"
(
        "I"  Integer  NOT NULL,
        "C"  Varchar (32) UNICODE, …
[Read more]
Synchronization Manager: MySQL as replication destination

Earlier this week, I wrote about the Synchronization Manager and gave a step-by-step tutorial on getting an initial scenario implemented. In this article, I’ll expand on the previous tutorial by introducing the concept of uni-directional synchronization.

Uni-directional participants act as destinations for replicated data. These participants are sometimes called “slaves,” because they are not capable of replicating changes to other members of the synchronization scenario. Theoretically, any RDBMS that provides an appropriate JDBC interface can participate as a replication destination with little effort on the part of the DBA. As an example of this, I have documented my experience creating a uni-directional MySQL participant.

One situation DBAs might use databases synchronized as uni-directional participants is when they want to provide information to clients …

[Read more]
Creating a Synchronization Management Scenario

This is a follow-up to my earlier article on the MaxDB Synchronization Manager. In the months since my prior article, the Synchronization Manager has proved itself production ready and capable of replicating real-world databases in demanding scenarios.

Take the following as theoretical and emperical examples of such scenarios (not necessarily in that order):

i) For its yearly trade show, a company needs to process user registration. Because of the high volume of attendees, there must be more than one system through which registration takes place. Therefore, the registration software is to run on multiple separate laptops. At the end of each day, the laptops synchronize their registration information with each other and a master registration database.

ii) In order to reduce human error and increase efficiency, a grocery store …

[Read more]
MaxDB series: when do we publish the next article?

Dear MySQL users, MaxDB users and friends,

it happened what we always told you what might happen: we did not make it to write an article for you in this week. Of course, this is not the end of the series. It will continue, but other duties might force us in the future to skip a week again. As a small “excuse” for you, we have written an FAQ like entry.

Can I recover a MaxDB backup on a different version and/or a different system?

It depends: the processor architecture and the MaxDB version must be compatible. Given these two main preconditions you can take a backup from one system and recover it on a different system. This is a common situation when you are planning to upgrade the database software and the server hardware in one step. In general, we do not recommend to do these two steps at once. The simple reason that we do not is, that you should never change two variables at once. This makes debugging extremly …

[Read more]
MaxDB series: when do we publish the next article?

Dear MySQL users, MaxDB users and friends,

it happened what we always told you what might happen: we did not make it to write an article for you in this week. Of course, this is not the end of the series. It will continue, but other duties might force us in the future to skip a week again. As a small “excuse” for you, we have written an FAQ like entry.

Can I recover a MaxDB backup on a different version and/or a different system?

It depends: the processor architecture and the MaxDB version must be compatible. Given these two main preconditions you can take a backup from one system and recover it on a different system. This is a common situation when you are planning to upgrade the database software and the server hardware in one step. In general, we do not recommend to do these two steps at once. The simple reason that we do not is, that you should never change two variables at once. This makes debugging extremly …

[Read more]
MaxDB series: SQL users continued

Dear MySQL users, MaxDB users and friends,

Several co-workers have spoken to me on the length of the MaxDB series postings. I fully agree that most postings are too long for a blog. But we do have a very eager plan to publish a complete online class. This is causing long postings and we can’t make them much shorter. We try to structure the articles in a similar way like a web page to make reading and navigating easier. Every posting has a table of contents, is devided into sections and has a fixed structure. For offline reading, printing and as a reference we will soon publish a PDF document with all postings of the series.

The experiment to use the medium of a blog for a class will continue as long as the readers do not complain. But we will add a “read more” link to the fixed structure of every posting. That means, we will present only the beginning of a posting on PlanetMySQL and you have to click on a “read …

[Read more]
Showing entries 11 to 20 of 65
« 10 Newer Entries | 10 Older Entries »