I'm currently setting up a Amazon RDS for PostgreSQL database and connection fails every single time. I've remade the Amazon RDS for PostgreSQL instance 3x now, both with default out of the box settings and custom settings, and even tried putting creds on pgAdmin, no dice. I've tested another database connection and it works just fine.
I'm setting it to be public accessible as well, with username and database both just "postgres". What am I doing wrong?
Related
I'm new to SQL Server. I was a postgres user before. I installed the default SQL Server on my local machine and I'm trying to get an old react with node js application of mine working with a SQL Server. When ever my frontend makes more than 1 call to the backend, if my SQL Server has admin privileges it throws
Error: 17810: Could not connect because the maximum number of '1' dedicated administrator connections already exists.
If not, it throws:
Error 18451: Only administrators may connect at this time.
I checked my database configs and it's set to MULTI_USERS, so I don't understand why I can't login without admin privileges. Can someone help me with this? I wasn't able to find anything online.
My NodeJS backend is using TypeORM to connect to the database
The dedicated administrator connection is a different kind of connection. It's not just "a connection being made by someone with administrative access". You would use the DAC when the SQL instance is having some kind problem, and you can't connect at all because resources are all tied up. SQL will reserve some resources especially for the DAC connection to make sure you can still connect.
A DAC connection can be made by specifying ADMIN: as part of your connection string, which will connect to the assigned DAC port.
You shouldn't use this for "routine" admin work. Just connect using a login with the required administrative server roles (eg, sysadmin). You definitely shouldn't use this as part of a regular application's connection string. You shouldn't be using a SQL Server sysadmin login either. Create a user with the appropriate permissions for your application, and don't use the admin connection.
Regarding your second issue: Make sure the instance wasn't set to start in single user or minimum configuration mode using startup flags. Note that this is for the whole instance, it's not the same as the configuration for an individual database.
I am doing the following step, to configure Aurora target DB, while migrating local SQL Server DB to Aurora DB in cloud:
https://docs.aws.amazon.com/dms/latest/sbs/CHAP_SQLServer2Aurora.Steps.ConfigureAurora.html
I am running these queries from SSMS. May I know what 'target_database' should I use? I tried the endpoint from RDS but it is not working. Please advise what I am missing.
Your target database is the database in AWS. In your case, it sounds like it's an RDS database instance. You'll need to create a new DMS target endpoint. Select the RDS instance from the dropdown, give it a unique name, and select the RDS engine (Aurora MySQL or PostgreSQL. Add any additional connection attributes, if desired. Test the connection and you should be all set.
Source: https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Endpoints.html
Today, I am using AWS EC2 DB Instance for my database (SQL Server).
I want to change the instance and instead to use RDS instance for my SQL Server.
In order to complete the migration from EC2 to RDS I need to pass the database with all its tables/stored procedures/types/views etc.
I tried to backup the database of the EC2 instance and then restore it in the RDS instance but I get the exception:
Moreover, I tried to generate a script of the EC2 instance DB and then run the script on RDS SQL Server connection but it failed to run many of the scripts because of permission exceptions.
I also found an article from the AWS documentation that shows that it is possible to upload a backup to S3 bucket. But I couldn't manage to understand how to restore the backup from the S3 bucket in the RDS instance.
Please, help me figure out how to do it? I belive it must be possible and easy somehow.
Thanks in advance.
I was going to process the cube deployment and found the error.
I changed the target server name from 'localhost' to this,and tried different way but in vain.
Here is the snap from my SSMS
You may have multiple issues going on but the first and foremost is you do NOT deploy SSAS Multidimensional [MDX] models to a SQL Database Engine Instance!
Unless you have a very odd configuration ATI-PC\MSSQLSERVER should point to the default MS SQL Server Database Engine Instance NOT an SSAS MDX instance!
The SSMS screen shot you show is for the local host connection you show is for a Database Engine with SQL Server Authentication (SA), which I would assume the instance is called MSSQLSERVER which is the default instance name.
1) What is your SSAS instance name?
2) Does your windows account have permissions? SSAS doesn't allow for SQL server authentication so it must be windows authentication.
3) Is SQL Browser running?
4) Have you configured SQL Browser to allow for the protocols and to allow connections from both Localhost and ATI-PC(InstanceName)?
to connect to Analysis Services Change the Server Type. When first launching SSMS you can do that via changing server type and then modifying the server name to the appropriate name.
If your SSMS is already open you can select "Connect" drop down and choose Analysis Services.
Check on your SQL Browser Configuration by Launching "SQL Server (Version) Configuration Manager" then step through the different areas as far as how to configure it is somewhat self explanatory and because you are deploying an AdeventureWorks cube I would surmise that the configuration would be earlier in you tutorial you are working on.
I am sure that you have 'SQL Browser' service running in services.msc. Still I doubt your account which you logged in has access to SSAS and also to connect to that underlying SQL Server. Try checking both for the access, if you selected deploy as service account check that account has access in SSAS. If still you have issues trying checking the eventvwr if you are getting any more errors. If it is development box try recycling SSAS services and try deploying?
I created a SQL Server instance on Amazon web services. I can remote into it ok.
I created a new login ID and password through the management app, but when I try to connect with the data source administrator in windows I am getting a login failed error. I have tried this several times so I am sure I am not putting the wrong password in.
I have another sql server set up that I can create a login ID and connect to fine.
Any suggestions on what to try?
A couple of things to check:
Have you opened up port 1433 (or your custom TCP port if you specified one) in the security group associated with your EC2 instance (I assume it's EC2 since you said you can remote in)?
Have you created both a SQL Server login and a database user? SQL Server requires two objects for a login: A server login object and a database user object. See more details here: https://msdn.microsoft.com/en-us/library/aa337545(v=sql.105).aspx.