If I have done functional partitioning in my database and have for example a database Transactions and a database Products and these are different database servers and there are references from tables in the Transactions schema to tables in the products: If I have a transaction that involves/updates/deletes rows from tables both databases is that executed within a two phase commit protocol and is that done automatically under the hood by MySQL or some how the client program has to be involved? In my understanding the client program has to be involved in XA transactions but my scenario is not of that kind. So how would that work?

In SSMS v19 I can successfully connect/login to a SQL server that is listening on the default port 1433 Server : server.env.domain.com,1433 Authentication : SQL Auth And I can query any of the databases hosted on this server. Does SSMS reveal the connection-string it is using to make this connection ? I've searched quite a bit and can't find it. Or is there an API I can call that would return the exact connection string used by SSMS ? I ask because I am unable to connect via another app located on the same client machine as SSMS. I would like to know exactly how SSMS is making its connection.

Naive Question Assume we have an Application which was originally written for ORACLE as DBMS. If I want write an intermediary layer that gives this application independence to be able to work with PostgreSQL DBMS - I presume that I would be required to perform the following : SQL : Application--> ODBC API (Oracle Wire Protocol) --> My Layer ---> ODBC API (PostgreSQL Wire Protocol) Response : Application-->ODBC API (Oracle Wire Protocol) ODBC API (PostgreSQL Wire Protocol) ----> PostgreSQL DBMS Response : Application-->ODBC API (PostgreSQL Wire Protocol) <---- PostgreSQL DBMS

I found out that when I connect to a remote SQL named instance (ServerA\instanceA) from SSMS installed on ServerB, it does connect without error, but it uses the Named Pipe protocol. I found that out when I noticed that the SQL named instance port (50002) was blocked by the Firewall. From SSMS (on serverB), I get an error when I try to connect to ServerA,50002 but it succeeded when I connect to ServerA\InstanceA. I googled it, but wasn't able to find any good documentation explaining why it works. I checked and I didn't see any alias or any particular configuration for ServerA. If you could help me understand how (and why) it works, I would appreciate.

I`m trying to modify and use powershell script from learn.microsoft.com in order to enable SQL Shared Memory protocol on a remote server. But my issue is instead of connecting to provided ManagedComputer and ServerInstance parameters, the script tries to execute it locally and I get below error:

# Load the assemblies



$smo = 'Microsoft.SqlServer.Management.Smo.'
$wmi = new-object ($smo + 'Wmi.ManagedComputer').

# List the object properties, including the instance names.
$Wmi

$uri = "ManagedComputer[@Name='']/ ServerInstance[@Name='MSSQLSERVER']/ServerProtocol[@Name='Sm']"
$Sm= $wmi.GetSmoObject($uri)
$Sm.IsEnabled = $true
$Sm.Alter()
$Sm

**Exception calling "GetSmoObject" with "1" argument(s): "Attempt to retrieve data for object failed for ManagedComputer 'my computer name."** Ive searched a lot for similar problems but none of the suggested solutions didnt help, as I want to enable the protocol on remote server and if it works, to automate the script by running on multiple instances. But for now, my aim is to make it work at least on one remote server. Will appreciate your thoughts on this.

I'm not all that familiar with networking or protocols and couldn't find a similar question here or elsewhere. One of my security people is asking whether SQL Server requires NetBIOS for Named Pipes. I found this article that says NetBIOS should be disabled, but it's rather old and not from a source I've heard of.

How can I find out which Transport Protocol MySQL is using? I know how I can [change it](https://dev.mysql.com/doc/refman/5.6/en/connection-options.html#option_general_protocol) but I don't know how to show the current one.

The current documentation refers only to version 3 of the wire protocol. However, there is the following note in the documentation: > For descriptions of the earlier protocol versions, see previous releases of the PostgreSQL documentation However, I can't find anything about previous versions of the wire protocol.

I have come across the following line in a text book (Database System Concepts Textbook by Avi Silberschatz, Henry F. Korth, and S. Sudarshan $6e$) page no. 686: > Thomas’ write rule allows schedules that are not conflict serializable > but are nevertheless correct. Those non-conflict-serializable > schedules allowed satisfy the definition of view serializable > schedules (see example box). What I understood from the above lines is that every schedule generated by timestamp protocol following Thomas's write rule is view serializable. Now let's take the following little schedule: $S: R_1(X), W_2(X), W_1(X)$. This schedule $S$ is allowed under timestamp protocol which follows Thomas's write rule. And serialization order is $R_1(X), W_1(X).$ But I was not able to prove that it is view serializable. Actually I think that it is non-view serializable because, 1. Consider serial order as $T_1, T_2$ Now final value of $X$ is being written by $T_2$. So not equivalent. 2. Next alternative serial order is $T_2, T_1$ here, $R_1(X)$ will read value of $X$ written by $T_1$ not original value which was there before start of both transaction. So this too is not view-equivalent. What is going wrong here? Please help me with this one.

Listener and service are up and running. In SQL Plus, if I connect with no login, and execute '**conn sys/pwd@host:port/sid as sysdba**', connection is established successfully. But if I connect **/ as sysdba** or with **username and password** , it always **throws ORA-12560: TNS:protocol adapter error**. What are the possible reasons for this ?

There was an ip change on the sql server and after that I cannot connect from other machines ssms but can connect locally . The firewall is disabled on the server and moreover its listening on port 1433 and all the network protocols are open named pipes, shared memory and tcpip. TCP/IP properties IPAII - TCP port set to 1433 and TCP Dynamic Ports are blank Am i missing something?

I have to find a database that will ensure the UDP replication intercontinental. 1. Do you know if there is any SQL database that will support UDP replication? 2. If not, can I use MySQL replication (TCP/IP protocol) intercontinental (from China to Switzerland)? Will this work fine? Won't be any meltdowns? How can I prevent them? 3. The master will be in China and the slave in Switzerland. If the slave will be down for a long period of time, and the logs used to update the replications will be too big or not enough, how can I handle the replication? What is the solution? Thank you and kind regards, Andreea

Why can I still use named pipes to connect to SQL Server even if it's been disabled? I'm on SQL Server 2016 doing the testing. I have recorded my operation in this youtube video: https://www.youtube.com/watch?v=4lvkbwsspZc Hope someone can point me the right direction.