If I want to change FQDN in TDengine database , how should I operate ?
after I changing my fqdn in /etc/taos.cfg
I found I couldn't restart my Taosd service.
May I know why and how should I operate?
after you change the fqdn in /etc/taos.cfg
you also need to change the /var/lib/taos/dnode/dnode.json
to make sure the value of fqdn is same
then restart TDengine database service, it gonna be okay
Related
I am trying to install MediaWiki version 1.31 localy and I have run into some issues that I cant get past by. Mainly when I input datatabe connection (I am trying to connect to PostgreSQL database) information it returns this error.
Thing is the port I am trying to connect is 5433 not 5432, also the names "template1" and "postgres" are not included in my input trough the dialogue screen - I dont know where they came from. "test1" is the name of the database I am trying to connect to.
Any help or advice how to get trough this error would be greatly appreciated. Thank you.
That the port you specify is not used while setting up the database schema in the first place is a long-standing known bug. One workaround is to run your database on the default port until you have wiki set up, then change it back to the port you want.
In order to create a new database, you need to connect to an existing database in the same cluster. 'template1' and 'postgres' are pre-existing databases (usually created at the time the cluster was created) commonly used to connect to in order to create a new database. These names are "well-known", you don't need to specify them.
Is it possible to connect LOCALHOST DatabaseEgnine without providing the computer name like MyComputerName\LOCALHOST ?
(I use SQL Server 2012 - Standard Edition installed)
MyComputerName\LOCALHOST is named instance called LOCALHOST on your computer. To connect to it you must either specify the instance name (and have the SQL Server Browser service running) or specify the listening port explicitly (and have the instance configured to listen to static port, non-default since default is dynamic ports). So any of the below will work:
.\LOCALHOST
localhost\LOCALHOST
local\LOCALHOST
127.0.0.1\LOCALHOST
machinename\LOCALHOST
.:<port>
localhost:<port>
127.0.0.1:<port>
etc
Is very unlikely you actually wanted to install a named instance called LOCALHOST. You probably didn't read the setup dialogs and misconfigured the instance name. My recommendation would be to install it again, choosing a default instance (ie. unnamed) or a more convenient and less confusing instance name.
you can use . as servername
e.g.
.\mssqlserver
.\sqlexpress
For Default Instance:::
(local) or . (it is a dot)
Named Instance:
(local)\InstanceName (or) .\InstanceName
Is it the location of the database. What other values can hostname take, besides localhost ?
Hostname in the context of MySQL refers to either the name of the server hosting the database, or the name of the client computer (trying to) connect to the database, depending on the context.
This link may be a starting point, but you really need to clarify your question. What specific problem are you trying to solve?
https://dev.mysql.com/doc/refman/5.5/en/privilege-system.html
I found this pretty weird thing when I first installed SQL Server 2008, for some reason there are two things that I want to get rid of and I can't:
If my computer name is, say, ABC, then I always have to connect to ABC/MSSQLSERVER for the server name when I log in from the SQL Server client, instead of using just using ABC, may I know how I can do that?
How can I default the DB so that if I have multiple DB on the server (System DB + my real DB), I can always default to use my real DB without saying "Use MyRealDB" every time?
Thanks a lot!
Regards,
Anyi
1) When installing, you picked a named instance.
2) In user admin, you can specify the default database per user.
What's happened here is that your SQL Server is installed as a named instance. To remedy this, you'll have to remove and reinstall SQL Server.
I need to convert a named instance of SQL server 2005, to a default instance.
Is there a way to do this without a reinstall?
The problem is, 2 out of 6 of the developers, installed with a named instance. So its becoming a pain changing connection strings for the other 4 of us. I am looking for the path of least resistance to getting these 2 back on to our teams standard setup.
Each has expressed that this is going to be, too much trouble and that it will take away from their development time. I assumed that it would take some time to resolve, in the best interest of all involved, I tried combing through configuration apps installed and didn't see anything, so I figured someone with more knowledge of the inner workings would be here.
I also wanted to convert a named instance to default - my reason was to access it with just the machine name from various applications.
If you want to access a named instance from any connection string without using the instance name, and using only the server name and/or IP address, then you can do the following:
Open SQL Server Configuration Manager
Click SQL Server Network Configuration
Click Protocols for INSTANCENAME you want to make available (i.e. SQLExpress)
Right-click TCP/IP and click Enabled
Right-click TCP/IP and go to Properties
Go to the IP Addresses tab
Scroll down to the IPAll section
Clear the field TCP Dynamic Ports (i.e. empty/blank)
Set TCP Port to 1433
Click Ok
Go to SQL Server Services
Right-click your SQL Server (INSTANCENAME) and click Restart
This will make the named instance listen on the default port. Note : You can have only one instance configured like this - no two instances can have same port on the IP All section unless the instance is a failover cluster.
As far as I know, no. One reason is the folder structure on the hard drive; they will have a name like MSSQL10.[instancename]
This is why a lot of companies store their applications' connection strings at the machine level instead of the application level.
Just take the connection string out of the source code entirely. Then have everyone put their connection string in their machine.config.
This has the added benefit of avoiding unnecessary app-specific environment logic, i.e. when you copy your application to the staging server, the staging server already "knows" what database to use.
The only way to change the instance name is to re-install - uninstall and install as default instance.
A lot of times I'll use client alias to point an application at a different sql server than the ones it's connection string is for, esp. handy when working on DTS or an application with a hard coded connection string. Have everybody use a commonly named alias, use the alias in the connection string and point the alias’s on each dev box to the to the different instances. That way you won't have to worry about if the server is the default instance or not.
You shouldn't ever really need to do this. Most software that claims to require the default instance (like Great Plains or Dynamics) doesn't actually.
If you repost with your situation (installed X, then Y, but need to accomplish Z) I bet you'll get some good workarounds.
I think you can migrate your data from Sql Server without having default instance installed. You can just specify the port number of your Sql Server instance in Oracle Sql Developer and you can connect just using the server name, not using the server name and the instance.
Like this:
connect to "MYSERVER, 1433"