67 results found

1. MSSQL hostname change for an existing MSSQL database server

   When a MSSQL database server is upgraded to a new version, the name can not be changed from within Plesk and it needs to be done manually into the Plesk database once the name is set on MSSQL side.

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Databases  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

   Thank you for your input. We will consider this functionality in upcoming releases ​if it will be popular. Everyone, please continue voting for this feature if you consider it important.
   —
   IG

2. Reverse arrows of database import/export icons

   change image of import or export from database because its create confusion

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Databases  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

   Thank you for your input. We will consider this feature in upcoming releases ​if it will be popular. Everyone, please continue voting for this feature if you consider it important.
   —
   IG

3. Better MSSQL handling

   • MS SQL Server 2012 Express via Plesk Installer is configured to use dynamic ports by default and this causes a warning in Tools & Settings > Database Serrvers. Packages installed through your installer should not cause a warning by default :)

   • Improve the behavior of field "Allow remote connections from", under Domains > domain.tld > Databases > User Management > username because the generated firewall rule is OFF by default; maybe this is by design, infact the field description states "Your changes in this list will be pre-moderated by your hosting provider.", but the admin doesn't get any notification about changes to be moderated (notification to be implemented in my opinion).

   • enable using instance names in connection strings: MS SQL Probe service is behind firewall by default, but this prevent using instance names in connection strings, even when instances are listening on a fixed port number. There is already a rule to block all TCP connections to MS SQL Server, and this should be enough.

   • MS SQL Server 2012 Express via Plesk Installer is configured to use dynamic ports by default and this causes a warning in Tools & Settings > Database Serrvers. Packages installed through your installer should not cause a warning by default :)

   • Improve the behavior of field "Allow remote connections from", under Domains > domain.tld > Databases > User Management > username because the generated firewall rule is OFF by default; maybe this is by design, infact the field description states "Your changes in this list will be pre-moderated by your hosting provider.", but the admin doesn't get any notification about… more

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Databases  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

   This is a valid request, so we’ll look into it. There is no ETA at the moment, but we would really appreciate you voting for this request so that we can accurately assess its popularity relative to other features. Thanks in advance!

   — rk

4. MariaDB Xpand. Horizontal Scaling of Both Writes & Reads.

   MariaDB Xpand Database. Horizontal Scaling of Both Writes & Reads.

   Horizontal Scaling Secret #1: Automatic Data Distribution

   As tables and indexes are created, they are automatically “sliced” and distributed across all the nodes in the cluster. This distribution utilizes 64 bit consistent hashing based on the data keys, so each slice’s location is predictable, as well as what data it contains, from a simple metadata map. So any transaction running on any node can access any data on the cluster from at most a single hop away, and the “lookup” to find that data is a local in-memory table in the RDBMS. Our multi-patented Clustrix Rebalancer automatically distributes data across the cluster, partitioning the data both horizontally (slices) and vertically (representations).

   Horizontal Scaling Secret #2: Automatic Fan-out of SQL Queries

   On the query side, the SQL language is declarative, and not trivially parallelized or scaled horizontally. ClustrixDB solves this problem by pre-parsing each query, and distributing compiled query fragments directly to the specific cluster nodes containing the requisite data. This allows data processing to be done locally, minimizing data movement, and only returning result-sets to the initiating node. This kind of query fragment forwarding is very fast, due to the metadata map of where all the data resides. We call this “bringing the query to the data, rather than the reverse.” And this also allows massive parallelism of queries; large queries get maximum parallelism, while many simultaneous queries get max concurrency across all the nodes in the cluster.

   Horizontal Scaling Secret #3: Automatic Data Rebalancing

   A big challenge of data distribution across shared-nothing systems is data imbalance and/or hotspots. A node’s storage can get full, requiring repartitioning table(s) and moving data to a new node (called “re-sharding” if it’s a sharded system), to create more space. Correspondingly, a node can experience contention of CPU or network access without the storage being exhausted. This kind of contention can happen if the data distribution isn’t granular enough, allowing too many simultaneous transactions to occur on a small segment of data. This is called a “hotspot,” and is automatically handled by the Clustrix Rebalancer as well. The Clustrix Rebalancer automatically notices usage patterns, and re-splits high-access data slices, moving half of the data slice in contention to another node.

   Basically, the three main issues with the horizontal scaling of SQL are automatically handled by ClustrixDB, neither requiring changes to the MySQL application, nor data maintenance to be handled by DevOps. Being able to horizontally scale your MySQL application without needing to shard represents a significant CAPEX and OPEX savings to your IT and DevOps budgets.

   MariaDB Xpand Database. Horizontal Scaling of Both Writes & Reads.

   Horizontal Scaling Secret #1: Automatic Data Distribution

   As tables and indexes are created, they are automatically “sliced” and distributed across all the nodes in the cluster. This distribution utilizes 64 bit consistent hashing based on the data keys, so each slice’s location is predictable, as well as what data it contains, from a simple metadata map. So any transaction running on any node can access any data on the cluster from at most a single hop away, and the “lookup” to find that data is a local in-memory table in… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Databases  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

5. Implement checking of the psa database for inconsistencies after adjusting the domain's settings

   In particular circumstances when a domain's hosting type is switched to No hosting and back to Website Hosting, the following issue occurs: https://support.plesk.com/hc/en-us/articles/360013744460
   It would be helpful to implement a tool for checking the psa database for inconsistencies after the domain's hosting type is switched

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Databases  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

6. Protect databse from removal

   Protect databse from accidental removal, so the database behaves in the same way as the following wordpress_e: greyed out so it cannot be deleted.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Databases  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

   Thank you for your input! We will consider this functionality in upcoming releases if it will be popular. Everyone, please continue voting for this feature if you consider it important.

   —
   IG

7. Please add ability to change the password of the psa_root admin for Plesk Onyx so we can connect to the psa database using port 8306

   Plesk Onyx is setting a random password for the psa admin database and the connection to port 8306 using the default admin password is not possible.There is no way of retrieving or reseting the psa database admin password which is causing big trouble if we want to connect to the psa database or want to change the default database using plesk repair

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   open discussion  ·  2 comments  ·  Databases  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close