I want to build five clients through two interconnected bridges to reach the other end of the server.
Just like this final result:
Final
I have tried a client to connect to the server through two interconnected bridges.
But unsuccessful.
Like this:
Test
Is there need additional route table or ARP?
Related
I am currently working on a project where I am trying to assign costs to applications rather than servers.
An application can have many servers, and a server can house many applications.
All the data is stored in one database.
AppID
AppName
Server
I have run a query to find how many servers each app has, but I need the query to return the list of associated servers as well as the number of them.
The sql query shows how many times a server appears in the table, ie it appears every time an application uses that server.
Does anybody know how can I return the servers associated with each application?
This may be a job for GROUP_CONCAT().
Try this:
SELECT AppID, AppName,
COUNT(*) Number_of_Servers,
GROUP_CONCAT(Server) Servers
GROUP BY AppID, AppName
Be careful, though: the last column of the result set is a (denormalized)
hello this is my mysql table
table_clients
client_id
client_username (UNIQUE)
client_password
now i want to get 5 servers and install mysql on each server and use this table on each 5 servers.
my question is: is there any way that all 5 servers connected to each other (by 1 request) and converted to 1 big server? i mean if there is one user with username (hiworld) in server 2, can not create it this user again in other servers !. (connect all 5 server with same table together and make them 1 big server) .. is it possible?
my queries are too big (2-3 bilion) and i want to share them between 3-4 servers but (make servers united) like when use 1 server )
How to create linked server MySQL
"Cross Linked Servers" a functionality that exists on Ms Sql is the type of thing your looking for.
You would need to do some sort of insert trigger that checked to see if the name existed on the other server.
But this will be slow plus there is a risk of two servers getting the same name at the same time and allowing the insert because when it checked the other name was not already there.
No real good way of doing this. One idea may be to have only one master table for the table_clients. Make it a master to slave relationship. Any time you have to do an insert you insert to the master table/database, then copy that data to the slave instances. But you would still have to cross link the servers for this to work. What you are describing would require waiting on 5 servers to tell if the name has already been used. This way you only have to check on one server.
i have my database database1 for my company.
i want to create another database for client's company.the client's company requirement is same as ours.so that i can use my database1 for creating their database.
In database1 there is a tables which i want to use in client's company database. so please tell me how i can reduced the redundancy by using only database1 for my company and client's company too??? or do you think i want to make replica of database1??? if i have to make replica of database1,then how i can make it in mysql???
please suggest me how i can use one Database structure for other database.
i need your help.please tell me the right way of doing these.
If there is no separate server requirement from your client then you can do as per below-
I am assuming that some master tables will be always same for you as well your client as you mentioned that both have same kind of project, so create 3 databases on same server-
master_db : It will keep generic information tables, which will be used by you as well your client and should keep same information for both-
client_db : It will store tables those keep information for client like client's order can be different, need logs those will be different etc.
your_db : It will keep tables those you need only.
Note: Further it will depend how you are using db/tables in your code. Multiple DB setup will work for you or not. As per me it should not be any issue.
I have a report where i have to use two servers for accessing two different tables data. For this i use 2 datasets, one for query A in server A, another for query B in Server B.
The result of query A which i used in Server A, has to be passed to Query B which is in Server B. I need to do this without using Linked Servers.
I i understood this correctly you are just passing paramaters between report from Server A and Server B and since for all the reports we just use SELECT statments or any storedprocedure fetching from diffrent servers should not be a problem and you don't need to create a linked server for that.
If you can post any error you are getting while achiveing this please feel free.
I have also used 3 dataset (3 diffrent servers) for generating report i didn't face any problem in that.
I have 2 Database in my VB.net application. I am using 1st database for daily operations. I would like to send one of the table records to online database. How Can I do that? First database is MSSQL Online database is MYSQL. I have created connections already using MYSQL .net connector.
Any Help will be appreciated.
Regards
Have a look at using a Linked Server instance on SQL Server to write the data to MySQL using the four name notation.
SQL SERVER – Explanation and Example Four Part Name
SQL Server Four-part naming
Ok here is a rough set of steps you need to follow
Query the MSSQL database and retrieve the data you want. Storing it in a DataTable may be the best option starting off.
Loop through the DataTable rows and build an INSERT statement that will be run against the MYSQL database.
Execute the command against the MYSQL db.
This is the basics of what you need to do to get a simple working system. Also take a look at Transactions as a way to manage the rollback of data when something goes wrong.
I'm assuming this is a research project If you are planning on using this code in a production system then i would look into a different alternative such as uploading data files to a service attached to the MYSQL database. This would allow you to batch and retry an import when something goes wrong.