Need advice about which tool to choose?Ask the StackShare community!

MSSQL

661
417
+ 1
3
Sybase

45
80
+ 1
10
Add tool

MSSQL vs Sybase: What are the differences?

<Write Introduction here>
  1. Storage: The basic difference between MSSQL and Sybase lies in the way they store data. MSSQL uses row-based storage, while Sybase uses page-based storage. In MSSQL, each row is stored individually, making it easy to retrieve specific pieces of data. On the other hand, Sybase stores data in fixed-size pages, which can impact the performance for certain types of queries.

  2. Indexing: In terms of indexing, MSSQL and Sybase differ in their approach. MSSQL uses a B-tree index structure, which allows for efficient searching of data within a table. Sybase, on the other hand, utilizes a hash-based indexing technique, which can be faster for certain types of queries, but may not be as efficient for range queries.

  3. Clustering: Another key difference between MSSQL and Sybase is in the way they handle clustering. MSSQL supports clustered indexes, which physically reorganize the data in the table to match the order of the index. In contrast, Sybase does not support clustered indexes but offers the concept of clustered tables, which organize the physical storage of tables in a specific order.

  4. Transaction Management: MSSQL and Sybase differ in their transaction management capabilities. MSSQL supports multiple active result sets (MARS), which allows for executing multiple batches on the same connection. Sybase does not have native support for MARS, which can impact the performance of certain applications that require this feature.

  5. Data Types: When it comes to data types, MSSQL and Sybase have some differences. MSSQL offers a wider range of data types compared to Sybase, which may be beneficial for applications that require specific data manipulation features. However, Sybase provides better support for large object types like text, image, and unitext.

  6. Partitioning: In terms of partitioning capabilities, MSSQL and Sybase have distinct differences. MSSQL supports table and index partitioning, allowing for better management of large datasets. Sybase, on the other hand, has limited partitioning capabilities, which may impact performance and scalability for applications that require extensive data partitioning.

In Summary, the key differences between MSSQL and Sybase include storage mechanisms, indexing techniques, clustering options, transaction management capabilities, supported data types, and partitioning capabilities.
Advice on MSSQL and Sybase
Needs advice
on
MSSQLMSSQL
and
MySQLMySQL

We are planning to migrate one of my applications from MSSQL to MySQL. Can someone help me with the version to select?. I have a strong inclination towards MySql 5.7. But, I see there are some standout features added in Mysql 8.0 like JSON_TABLE. Just wanted to know if the newer version has not compromised on its speed while giving out some add on features.

See more
Replies (2)
Rafey Iqbal Rahman
Recommends
on
MySQLMySQL
at

MySQL 8.0 is significantly better than MySQL 5.7. For all InnoDB row operations, you'll see a great performance improvement. Also, the time taken to process transactions is lower in MySQL 8.0. Moreover, there has been an improvement in managing read and read/write workloads.

See more
Jeremy Jones
Digital Developer at SpeakUnique · | 6 upvotes · 313.6K views
Recommends
on
MySQLMySQL

MySQL AB doesn't implement anything in MySQL until they can find a way to do it efficiently and, often, more efficiently than other systems. So although I don't have experience with benchmarking JSON_TABLEs or similar new features, their development philosophy alone suggests that version 8 for the latest features would be a safe jump without sacrificing system performance.

See more
Decisions about MSSQL and Sybase
Kyle Harrison
Web Application Developer at Fortinet · | 21 upvotes · 446.1K views

While there's been some very clever techniques that has allowed non-natively supported geo querying to be performed, it is incredibly slow in the long game and error prone at best.

MySQL finally introduced it's own GEO functions and special indexing operations for GIS type data. I prototyped with this, as MySQL is the most familiar database to me. But no matter what I did with it, how much tuning i'd give it, how much I played with it, the results would come back inconsistent.

It was very disappointing.

I figured, at this point, that SQL Server, being an enterprise solution authored by one of the biggest worldwide software developers in the world, Microsoft, might contain some decent GIS in it.

I was very disappointed.

Postgres is a Database solution i'm still getting familiar with, but I noticed it had no built in support for GIS. So I hilariously didn't pay it too much attention. That was until I stumbled upon PostGIS and my world changed forever.

See more

I happen to point my asp.net core web application from MSSQL to MySQL due to infrastructure costs associated with the former db. The application also had challenges creating a migration schema of asp.net membership on MySQL.

After a thorough research I figured out how to do it and also made a video and uploaded to youtube. You can check that here https://youtu.be/X4I0DUw6C84

The full source code for the demo template is available on github here http://bit.ly/2LWgacA

See more
Manage your open source components, licenses, and vulnerabilities
Learn More
Pros of MSSQL
Pros of Sybase
  • 3
    Easy of use
  • 1
    Sybase has at least 200000 from 15 years ago
  • 1
    Verry fast queries response
  • 1
    SAP Replication server este net superior replicarii din
  • 1
    Configurable with 2k,4k,8k,16k,32k data pages
  • 1
    Very good for application with high number of connectio
  • 1
    Replication server the best
  • 1
    HADR dont loose data
  • 1
    Max number of connection is 350000
  • 1
    HADR does not lose data is superior to Allwayson which
  • 1
    SAP Replication server is clearly superior to MS SQL Se
  • 0
    Multiple pools pools
  • 0
    Multiple buffer pools

Sign up to add or upvote prosMake informed product decisions

Cons of MSSQL
Cons of Sybase
  • 1
    License Cost
  • 1
    Vendor lock-in
    Be the first to leave a con

    Sign up to add or upvote consMake informed product decisions

    What is MSSQL?

    It is capable of storing any type of data that you want. It will let you quickly store and retrieve information and multiple web site visitors can use it at one time.

    What is Sybase?

    Modernize and accelerate your transaction-based applications on premise and in the cloud. This high-performance SQL database server uses a relational management model to meet rising demand for performance, reliability, and efficiency in every industry.

    Need advice about which tool to choose?Ask the StackShare community!

    What companies use MSSQL?
    What companies use Sybase?
    Manage your open source components, licenses, and vulnerabilities
    Learn More

    Sign up to get full access to all the companiesMake informed product decisions

    What tools integrate with MSSQL?
    What tools integrate with Sybase?

    Sign up to get full access to all the tool integrationsMake informed product decisions

    What are some alternatives to MSSQL and Sybase?
    MySQL
    The MySQL software delivers a very fast, multi-threaded, multi-user, and robust SQL (Structured Query Language) database server. MySQL Server is intended for mission-critical, heavy-load production systems as well as for embedding into mass-deployed software.
    PostgreSQL
    PostgreSQL is an advanced object-relational database management system that supports an extended subset of the SQL standard, including transactions, foreign keys, subqueries, triggers, user-defined types and functions.
    Oracle
    Oracle Database is an RDBMS. An RDBMS that implements object-oriented features such as user-defined types, inheritance, and polymorphism is called an object-relational database management system (ORDBMS). Oracle Database has extended the relational model to an object-relational model, making it possible to store complex business models in a relational database.
    IBM DB2
    DB2 for Linux, UNIX, and Windows is optimized to deliver industry-leading performance across multiple workloads, while lowering administration, storage, development, and server costs.
    MongoDB
    MongoDB stores data in JSON-like documents that can vary in structure, offering a dynamic, flexible schema. MongoDB was also designed for high availability and scalability, with built-in replication and auto-sharding.
    See all alternatives