https://eureka.patsnap.com/resources/blog/rd-blog/database-merge-join-algorithm-for-sorted-input-streams-patent-landscape/ · Patsnap · data cut-off 2026-10-26 · downloaded from the live page
Patent Landscape · Database Technologies

Database Merge Join Algorithm Patents for Sorted Input Streams

Analysis of 34 patent families on merge join algorithms for sorted database streams, led by IBM with 8 families.

72
Published Records
34
Simple Patent Families
35%
In Force at Cut-off
US
Leading Jurisdiction

72 published records collapse into 34 simple (DOCDB) families; the difference is the same invention filed in more than one country. In force = 25 of 72 records still granted and maintained at the data cut-off; the rest are pending, withdrawn, refused or lapsed.

  • 34 simple patent families and 72 published records sit in scope here, with no date limit applied to the search string.
  • International Business Machines Corporation is named on 8 of the 34 families, the highest single-row count, while 17 of the 20 listed filers hold 2 or fewer families each.
  • Published records filed under the Patent Cooperation Treaty route through WIPO account for 5 of the records seen, alongside 48 filed at the United States receiving office.
Check your own idea
Published byPatsnap Research··6 min readSourced from Patsnap Eureka
Overview

What this search covers

This page tracks records matching database, merge join and a sort-related term across titles, abstracts and claims. The search returns 34 simple patent families and 72 published records, with every subclass tagged against the underlying technology, and every filer counted on a family basis rather than a record basis. Merge join here refers to the relational-database operation that combines two pre-sorted input streams on a join key without a separate hash step.

34 families is a small pool. Treat this page as a starting point for a deeper search rather than a map of the field: a handful of documents can shift a share by several percentage points, and absence of a term in the search string is as likely to explain a gap as absence of filing activity.

Records by filing year (published records, not de-duplicated by family)
  1. INTERNATIONAL BUSINESS MACHINE CORPORATION8
  2. TERADATA US INC5
  3. ORACLE INT CORP3
  4. HEWLETT PACKARD ENTERPRISE DEV LP2
  5. MICROSOFT TECHNOLOGY LICENSING LLC2
  6. HUAWEI TECH CO LTD2
  7. SAP SE1
  8. META PLATFORMS INC1
  9. SOFTBANK GROUP CORP1
  10. MICRO FOCUS LLC1

Counted over all 72 published records, including filings from before 2007; the filing-trend chart below covers only the 54 records from 2007 onward, so the two charts are not the same set of documents. Ordered by volume only, not by importance or claim strength. Counted in simple (DOCDB) patent families, so one invention filed in several countries counts once. Names come from Patsnap's standardised assignee field as recorded on each document; subsidiaries and group companies are not merged. The icon before each name is read from the name itself (words such as University, Institute or Ltd); the data carries no organisation-type field, so treat it as a reading aid rather than a classification. 2 rows in this table start with the same name (HEWLETT PACKARD ENTERPRISE DEV LP, HEWLETT PACKARD CO). They are left as separate rows, so the largest-filer figure above is per legal entity, not per group. Rows that look related still cannot be added together: one family can name several of them. Filings held by named individuals rather than organisations are removed where they can be identified (1 here); that identification is not exhaustive, so an individually held filing can still appear below. Either way those filings stay inside the totals above. This table shows the top 20 of the 20 filers returned for this search; the data endpoint returns at most 100 entities, so even that 20 is not the complete set of filers. A single family can name more than one filer, so these counts overlap and do not add up to the total.

Source: Patsnap Eureka. Assignee ranking and totals. Derived from one Patsnap search for Database Merge Join Algorithm for Sorted Input Streams Patent Landscape, covering all matching records regardless of filing date (the search string sets no date limit), retrieved 2026-10-26. Counts cover published records only and move as new filings publish.Run this in Eureka MCP
Data

Filing trend and technology composition

The chart below counts published records by earliest filing year; the table counts IPC subclasses against the 34 families in scope.

Filing trend by earliest filing year (54 of 72 published records)

Records run from 2007 (4) to a peak of 12 in 2021, then taper into 2026. The stretch from 2022 onward is still filling in as later filings publish, so the last few years understate eventual counts and should not be read as a drop in activity.

Filing trend by earliest filing year (54 of 72 published records)036912420072009201120132015201720191220212023202512022 onwards are shaded as still filling in: a filing is only visible once it publishes, up to 30 months after filing.

Counted in published records by earliest filing year, not de-duplicated into families. A filing is counted in the year it was filed, but it only becomes visible after it publishes: roughly 18 months for most routes, and up to 30 months where a PCT application enters national phase. 2022 onwards are therefore still filling in and are shaded; no growth figure on this page uses them. Because this series counts documents rather than inventions, a rise can mean more inventions or the same inventions filed in more countries; this dataset cannot separate the two. This chart covers 2007-2026 (54 records); the 72 total quoted above includes earlier filings outside the window.

IPC subclass coverage

G06F (Electric digital data processing) appears on all 34 families in scope, which is expected given the search string targets a database operation. A handful of other subclasses appear on the chart at low shares; none of them clears a level worth describing in prose.

IPC subclass coverageG06F · Electric digital data processi…34100.0%G06N · Computing based on AI models25.9%G06Q · Business, commerce & admin dat…12.9%H04L · Digital information transmissi…12.9%

Shares are the percentage of the 34 patent families in scope. One patent family can carry several IPC classes, so the shares add up to more than 100%.

Source: Patsnap Eureka. Filing trend and technology composition. Derived from one Patsnap search for Database Merge Join Algorithm for Sorted Input Streams Patent Landscape, covering all matching records regardless of filing date (the search string sets no date limit), retrieved 2026-10-26. Counts cover published records only and move as new filings publish.

Go deeper on Database Merge Join Algorithm for Sorted Input Streams Patent Landscape with Eureka

This page is one run against one query. Ask Eureka your own question about database merge join algorithm for sorted input streams patent landscape and every answer comes back with the patent numbers behind it.

Try Eureka
Example record

A record from the result set

First record returned
US5089985A1992-02-18

System and method for performing a sort operation in a relational database manager to pass results directly to a user without writing to disk

INTERNATIONAL BUSINESS MACHINES CORPORATION

In a relational database system, a method is used that increases the performance of the sort operation. An optimiser routine in the relational database manager analyses a user's complete query to determine whether the final sorted results can be used directly by the user as sorting occurs. If the sort results can be used, the sort results are sent to Relational Data Services in the relational database manager for output to the user. Depending upon the determination made by the optimiser routine, one of two output modes for the final sorted sequence string of data are selected by the relational database manager.US5089985A, International Business Machines Corporation, filed 1992-02-18. This is the first record returned under the database's default ordering, not a ranking by citations, breadth or date.

US5089985A, patent drawing 1US5089985A, patent drawing 2
View full record

Selected as the first record the search returns under the database default order, then shown in full. It is not ranked by citations, claim breadth or commercial importance, and it is not a judgement about which filing in this space matters most.

Source: Patsnap Eureka. The first record the search returned, shown in full. Derived from one Patsnap search for Database Merge Join Algorithm for Sorted Input Streams Patent Landscape, covering all matching records regardless of filing date (the search string sets no date limit), retrieved 2026-10-26. Counts cover published records only and move as new filings publish.Run this in Eureka MCP
Run it yourself

Put your own technology through the same analysis


  
Where to run it
Fastest

Eureka on the web

When you want the answer in the next five minutes.

The agent works the prompt against patents and technical literature, citing every source.

Run your analysis now →
For builders

MCP server & REST API

When it has to run inside your own pipeline.

Patent search, landscape analysis and assignee resolution as MCP tools. Drop them into any agent framework, or call REST directly.

Browse MCP servers →
Key figures

What the numbers show

Three figures worth checking before searching further.

Scope
34 families / 72 records
simple patent families / published records

Family and record counts

The search returns 34 simple patent families and 72 published records, with no date limit applied. A simple family can produce several published records across receiving offices, which is why the record count runs higher than the family count.

No date restriction was applied to this search
Filer concentration
8 of 34 families
largest single-row count

Largest listed filer

International Business Machine Corporation is named on 8 of the 34 families (23.5%). Two further rows in the listed filers begin with the name Hewlett Packard and are listed separately; they are not summed with each other or with any other row.

Filer rows are not rolled up to corporate group
Long tail
17 of 20 listed filers
hold 2 or fewer families each

Spread across the listed filers

Of the 20 listed filers, 17 hold 2 or fewer simple patent families each. Because one family can name more than one filer, these rows cannot be added together into a combined share.

Filer rows overlap; counts are not a partition of the 34 families
Legal status
25 of 72 records
granted and in force at retrieval

In-force snapshot

25 of the 72 published records were granted and in force at the retrieval date of 2026-10-26. The remaining records are in other states not broken out here, and legal status changes continuously after retrieval.

Status is a snapshot, not a success rate
Eureka AI Agent
Looking for what nobody has claimed yet?

Eureka can read the same corpus for gaps instead of for coverage: under-claimed branches adjacent to database merge join algorithm for sorted input streams patent landscape, with the prior art for and against each one.

Find the white space →
Source: Patsnap Eureka. Derived observations on the same dataset. Derived from one Patsnap search for Database Merge Join Algorithm for Sorted Input Streams Patent Landscape, covering all matching records regardless of filing date (the search string sets no date limit), retrieved 2026-10-26. Counts cover published records only and move as new filings publish.Run this in Eureka MCP
Next steps

Where to take this search next

This page is a starting point built from one search string. The next steps depend on what you need to check.

Read the granted claims directly

A family count or an abstract cannot establish claim scope. Pull the granted claim set for any record that matters before drawing a conclusion about what it covers.

Open the record in Eureka

Widen or narrow the search string

A 34-family pool is small enough that different sort- or join-related terms could move the scope meaningfully. Try adjacent phrasing to see how the count and the filer list change.

Refine the search in Eureka

Check filer rows individually

Filer names here are not rolled up to corporate group, so a parent and its named subsidiaries sit on separate rows. Check each row on its own terms before drawing any conclusion about a group.

Explore filers in Eureka
Source: Patsnap Eureka. Suggested next steps. No new data: every figure named here is one of those above. Derived from one Patsnap search for Database Merge Join Algorithm for Sorted Input Streams Patent Landscape, covering all matching records regardless of filing date (the search string sets no date limit), retrieved 2026-10-26. Counts cover published records only and move as new filings publish.Run this in Eureka MCP
FAQ

Frequently asked questions

Answers are grounded in the same dataset. Derived from one Patsnap search for Database Merge Join Algorithm for Sorted Input Streams Patent Landscape, covering all matching records regardless of filing date (the search string sets no date limit), retrieved 2026-10-26. Counts cover published records only and move as new filings publish.Run this in Eureka MCP

Research Database Merge Join Algorithm for Sorted Input Streams Patent Landscape in depth with Eureka

Go past this page: query the whole database merge join algorithm for sorted input streams patent landscape corpus yourself, in your own scope.
Every answer comes back with patent numbers you can open.

Try Eureka
How this page was built, and what the numbers do and do not mean

Search. Every figure on this page comes from one Patsnap search, run once and not edited afterwards. This is the exact search string:

TAC:((database) AND ("merge join") AND (sort* OR "sorted input"))

Reading the field codes: TAC searches the title, abstract and claims of each record, not the full description. The search string sets no date limit, so the scope is every matching record in the database regardless of when it was filed. It is not restricted to recent years. How this string was built matters for how far the counts can be pushed. It was generated in batch from a topic list rather than hand-crafted for this page, and the result set is not manually screened. A keyword search over title, abstract and claims both over-captures (unrelated filings that happen to use the same words) and under-captures (the same invention written in different words). This page cannot measure either effect, so read every figure here as what this particular string returned, not as what exists in the field. One subclass (G06F) carries 100.0% of the patent families, so this search returned a classification-tight set.

What is being counted. Two different units appear on this page and they are not interchangeable. The filer list and the technology split are counted in simple (DOCDB) patent families: one invention counts once however many countries it was filed in. The total, the jurisdiction split and the filing-year chart are counted in published records: the same invention counts once per publication. For this search that is 72 records and 34 families. Record counts reward filing in many jurisdictions; family counts do not. Shares are only ever taken against a denominator in the same unit, and each one names it.

Who the filers are. Names come from Patsnap's standardised assignee field, as recorded on the documents themselves. They are not rolled up to corporate group: a parent and its subsidiaries appear as separate entries, and a portfolio acquired from another company stays under the name on the document unless the assignment is reflected there. This list is meant to carry organisations, not people. Filings held by a named individual are identified by matching the assignee against the inventors on the same search, and, for names written in Chinese, Japanese or Korean characters, by the name carrying no organisational suffix; those are removed from the list (1 of them here). Neither test is exhaustive: the inventor list it matches against is itself capped, and a personal name written in Latin script with no organisational wording in it cannot be told apart from a short company name by rule. So an individually held filing can still appear in the list. Those filings stay inside every total and share on this page either way, so the listed entries can add up to less than the total. A record shown in full further down still names its assignee exactly as the patent office records it, including where that is a person: that name is how the record is identified and checked. What is left out of the ranking is people as ranked entries, not people as cited sources. The table shows the top 20 of the 20 filers returned, ordered by count alone; the data endpoint returns at most 100 entities, so even that 20 is not every filer. One patent family can name several filers and each is counted separately, so these rows are not slices of a divided whole: adding them together over-counts, and this page deliberately publishes no combined "top five" share for that reason. See every filer, individuals included

Dates. The year chart counts by earliest filing year, not publication year. A filing only becomes visible once it publishes: roughly 18 months for most routes, and up to 30 months where a PCT application enters national phase. Measured across these pages, the year four back from today still holds only about 89% of its eventual count. 2022 onwards are therefore shaded on the chart as still filling in. The data behind this page was retrieved on 2026-10-26.

Legal status. "In force" counts documents whose legal status at retrieval was granted and maintained (25 of 72). Everything else is pending, withdrawn, refused, lapsed or not determinable, and those states are not broken out here because the underlying codes do not separate them cleanly. Legal status changes continuously and is reported per document, not per family. Get the status breakdown in Eureka

Classification. The technology split uses IPC subclasses (four characters, for example H01M). A single record usually carries several, so the shares add up to more than 100% and a record can appear in more than one bar. Subclass is a coarse grouping; it describes the field a record was classified into, not what the claims cover. Break the classes down to subgroup level

Who wrote the words. The tables, charts, counts, shares and patent numbers on this page are produced directly from the search result by a program; none of them are written or estimated by a language model. The surrounding prose, headings, FAQ answers and the answers in the question panel are drafted by a language model that is given those same figures and is not permitted to introduce others. Prose can still mis-describe a correct figure, so where the two disagree, the tables and charts are the record.

Disclaimer. This page is generated from Patsnap Eureka data drawn from a limited snapshot of global patent and scientific-literature records, and is provided for general information and reference only.

Patent data carries limitations that apply to every figure above. Recent filings are under-counted, because an application is not public until roughly 18 months after filing and database loading adds further delay. The search string defines and constrains everything shown: records that use different terminology, or that sit outside the fields searched, are absent and cannot be counted. Applicant names, classification codes, legal-status codes and citation records are taken as recorded and may contain errors, duplicates, omissions or stale entries. Ordering by volume is not a measure of quality, scope, enforceability or commercial value, and a larger portfolio is not a stronger one. As a result, the analysis may be incomplete or inaccurate and may not reflect the full technology landscape.

Nothing on this page constitutes an exhaustive prior-art, novelty, freedom-to-operate, validity or infringement search, nor does it constitute legal, financial, investment, or professional advice, and it should not be relied upon as such. No attorney-client relationship is created by it. Any patent, commercial, or strategic decision should be verified independently against the primary records and reviewed with qualified patent, legal, and domain professionals. Patsnap makes no warranties, express or implied, as to the accuracy, completeness, or fitness for any particular purpose of the information presented.

The question panel. The answers behind the suggested questions on this page were written when the page was generated, not in response to your click. The progress steps that play before an answer appears are an animation of how that analysis was done; nothing is being searched or computed at that moment. Typing your own question instead opens Patsnap Eureka, which does run it live.

Help us improve

Something wrong, out of date, or missing on this page? Tell us and it goes straight to the team that maintains it.