Nicklee. Framework. v.1.8.1 overall architecture supports distributed queries and distributed transactions
You can write the distributed syntax supported by sqlserver in XML in the data layer of the framework.
For example:
Select *
From OpenDataSource (
'Sqlodb ',
'Data source = 192.168.xx.xx; user id = sa; Password = Sa'
). Northwind. DBO. categories as
Left join northwind. DBO. categories as B on A. categoryid = B. categoryid
Or
Select *
From OpenDataSource (
'Sqlodb ',
'Data source = 192.168.100.xx; user id = sa; Password = Sa'
). Northwind. DBO. categories as [A]
Left join
OpenDataSource (
'Sqlodb ',
'Data source = 192.168.100.xx; user id = sa; Password = Sa'
). Northwind. DBO. categories as [B]
On a. categoryid = B. categoryid
Left join
-- Full path restriction is required.
Northwind. DBO. categories as [c]
On C. categoryid = B. categoryid
Or use the method described by frog.
Method 2:
Use the connection server first:
Exec sp_addmediaserver 'Alias ', '', 'msdasql', null, null, 'driver = {SQL Server}; server = remote name; uid = user; Pwd = password ;'
Exec sp_add1_srvlogin @ rmtsrvname = 'aliased ', @ useself = 'false', @ locallogin = 'sa', @ rmtuser = 'sa ', @ rmtpassword = 'Password'
Go
Then you can:
Select * from alias. Database Name. DBO. Table Name
Insert database name. DBO. Table Name select * from alias. Database Name. DBO. Table Name
Select * into database name. DBO. New table name from alias. Database Name. DBO. Table Name
Go
To put it simply, data mining, data collection, OLAP, distributed queries, and distributed transactions can be achieved by SQL Server T-SQL. Now, in nicklee. framework. v.1.8.1 the data layer of the overall architecture is supported and more flexible, nicklee. framework. v.1.8.2 the overall architecture will provide specific examples of distributed queries and distributed transactions. If you have enough skills, you can touch them yourself. I believe there is a different experience.
To put it more simply, all the queries passed in the query analyzer can be written in XML.