I used PostgreSQL briefly, many, many years ago for some very simple personal databases but then moved to SQLite for it's administration. However I now want to use some large datasets and would like to use Postgres. I only want a single user on a local machine to have access to Postgres and the databases on an Ubuntu based pc. Nearly all the tutorials I've read assume that multiple, networked users will want access. From what I remember, I think Postgres is installed with only local access. How do I lockdown Postgres to a single, local user? 1) I need an administrator account. According to https://www.postgresql.org/docs/17/postgres-user.html : 'Pre-packaged versions of PostgreSQL will typically create a suitable user account automatically during package installation.' So the administrator is called postgres and created automatically 2) I create non-administrative regular database user (called MyUser here) to access databases but not administer PostgreSQL. 3) I do not have to be concerned with Preventing Server Spoofing (https://www.postgresql.org/docs/17/preventing-server-spoofing.html) because MyUser will be the only user. 4) From https://www.postgresql.org/docs/current/auth-pg-hba-conf.html , pg_hba.conf should ONLY contain:

# Allow any user on the local system to connect to any database with
# any database user name using Unix-domain sockets (the default for local
# connections).
#
# TYPE   DATABASE        USER            ADDRESS                 METHOD
  local  all             MyUser                                  trust

5) It is noted in the same page as 3): 'Remote TCP/IP connections will not be possible unless the server is started with an appropriate value for the listen_addresses configuration parameter, since the default behavior is to listen for TCP/IP connections only on the local loopback address localhost.' So I do NOT need to use 'localhost' in the 'pg_hba.conf' file, according to https://stackoverflow.com/questions/11913897/ 6) I saw this article, https://stackoverflow.com/questions/24531420/ (I am in a similar situation as this user except I'm using Linux). Do need give access to port 5432, or is this done at setup? Is there anythjing else I should consider or is there a tutorial for a single local user? Thank you for any help.

When trying to install SQL Server 2022 from iso, I can't get setup wizard doing a single (visible) action when I click the "New SQL Server standalone installation" link. Everything seems being blocked at landingPage.exe startup. All I can get from C:\Program Files\Microsoft SQL Server\160\Setup Bootstrap\Log is the following:

(01) 2022-12-14 08:38:52 Slp: Completed Action: ExecuteBootstrapAfterExtensionsLoaded, returned True
    (01) 2022-12-14 08:38:52 Slp: ----------------------------------------------------------------------
    (01) 2022-12-14 08:38:52 Slp: Running Action: LandingPage
    (01) 2022-12-14 08:38:52 Slp: Landing page action
    (01) 2022-12-14 08:38:52 Slp: Starting Landing Page: Path = D:\x64\LandingPage.exe, Arguments =  /ENU /MEDIASOURCE="D:\\"

LandingPage summary is the following:

Overall summary:
      Final result:                  Passed
      Exit code (Decimal):           0
      Start time:                    2022-12-14 08:38:50
      End time:                      2022-12-14 08:48:19
      Requested action:              LandingPage
    
    Machine Properties:
      Machine name:                  XXXXXXXXXX
      Machine processor count:       8
      OS version:                    Microsoft Windows 10 Entreprise (10.0.19044)
      OS service pack:               
      OS region:                     United States
      OS language:                   français (France)
      OS architecture:               x64
      Process architecture:          64 Bit
      OS clustered:                  No
    
    Package properties:
      Description:                   Microsoft SQL Server 2022 
      ProductName:                   SQL Server 2022
      Type:                          RTM
      Version:                       16
      SPLevel:                       0
      Installation location:         D:\x64\setup\
      Installation edition:          
    
    Notice: Please read Microsoft SQL Server Software License Terms at aka.ms/useterms.
    
    User Input Settings:
      ACTION:                        LandingPage
      CONFIGURATIONFILE:             
      ENU:                           true
      HELP:                          false
      IACKNOWLEDGEENTCALLIMITS:      false
      INDICATEPROGRESS:              false
      QUIET:                         false
      QUIETSIMPLE:                   false
      SUPPRESSPAIDEDITIONNOTICE:     false
      SUPPRESSPRIVACYSTATEMENTNOTICE: false
      UIMODE:                        Normal
    
      Configuration file:            C:\Program Files\Microsoft SQL Server\160\Setup Bootstrap\Log\20221214_083850\ConfigurationFile.ini
    
    Rules with failures or warnings:
    
    Rules report file:               The rule result report file is not available.

I previously installed SQL Server 2022 CTP2 on the same machine, but I chose to remove all the stuff prior to set the RTM version up, and all went fine at the time :/ What am I supposed to do to make it installed? Thanks,

Hi we are using PostgreSQL 16 on Ubuntu 22 LTS and have built a cluster using initdb. I'm wondering if it's possible to rebuild a standby using pg_createcluster instead to take advantage of various admin tools and join it to the cluster so that we can eventually failover (we use repmgr), and then remove the old nodes and rebuild them using pg_createcluster as well. As I understand it pg_createcluster is essentially a wrapper around initdb. Unfortunately being in production, simply rebuilding the entire cluster is a no-go, so our choice is to either live with it having been built using initdb, or add/remove nodes until the entire cluster is rebuilt with pg_createcluster.

I am using oracle database 12c and would like to setup TCP SSL connection to be able to connect using the same machine where the database is hosted. So, connection would be from database machine to itself using SSL. I believe there has to be some setup to the oracle wallet file but not quite sure what is the proper way to create the certificates since it will be on the same machines. Most tutorials show steps for a client to server setup, but I want a local setup. Any help/guidance is appreciated. Thanks!

## PREFACE (EDIT): *Per comments on my original post, this question has been modified to focus on the **PostgreSQL**-specific elements of my goals. A separate question for the **MySQL** version has been posted here: **[MySQL Database Setup Script(s) - Limiting Created User Access](https://dba.stackexchange.com/q/314429/26130)*** (*mostly a copy/paste of this question but with SQL "scripts" specific to that RDBMS*) --- I'm building a stand-alone application for which I will be giving users the option of storing information in one of three (currently) database systems: **PostgreSQL**, **MySQL**, or **SQLite**. I'm not *actually* a DBA, but I've had some experience with setting up databases and such for my development projects over the years. Obviously, as a part of the initial setup, I'm going to need to create the required structure in the chosen database system. For the **PostgreSQL** and **MySQL** options, I'm also creating groups/users to access the new structure, but I'm wanting to impose restrictions on data access, both for the newly created users and for existing users. What I'm wanting is: 1. My new users should *only* have access to the new structure and objects I create. They should not be able to access any existing structure that may be present in the RDBMS to avoid potential security risks and such. 2. Existing users should not be able to access my new structure or objects. I'm not storing any personal or particularly "sensitive" information anywhere, but I'd prefer users not be able to just go in and change the structure or data manually. For **SQLite**, this isn't necessarily a problem - I'm encrypting the database file and, since **SQLite** doesn't have the concept of "users", that's about the best I can do. But for **PostgreSQL** and **MySQL**, I just want to make sure I get it "right". During initial setup I'll be creating the following roles: MyAppDevelopers (*group*), MyAppAdmin (*user*), and MyAppUser (*user*). The application user will have to provide a set of credentials for an existing user that has the CREATE ROLE and CREATE DATABASE permissions. If it's a new PostgreSQL installation, they'll be prompted to set up a password for the postgres user instead, which should have all the permissions it needs. For the role creation part, I have this (*simplified from a DO procedure that simulates the IF NOT EXISTS clause*):

--
-- Name: MyAppDevelopers; Type: ROLE;
--
CREATE ROLE "MyAppDevelopers" WITH
	NOLOGIN
	NOSUPERUSER
	INHERIT
	NOCREATEDB
	NOCREATEROLE
	NOREPLICATION;

COMMENT ON ROLE "MyAppDevelopers"
	IS 'User group for application users from My App Development';

--
-- Name: MyAppAdmin; Type: ROLE;
--
CREATE ROLE "MyAppAdmin" WITH
	LOGIN
	NOSUPERUSER
	INHERIT
	CREATEDB
	NOCREATEROLE
	NOREPLICATION
	IN ROLE "MyAppDevelopers"
	PASSWORD '#APASS#';

	COMMENT ON ROLE "MyAppAdmin"
		IS 'PostgreSQL user for My App database administration';

--
-- Name: MyAppUser; Type: ROLE;
--
CREATE ROLE "MyAppUser" WITH
	LOGIN
	NOSUPERUSER
	INHERIT
	NOCREATEDB
	NOCREATEROLE
	NOREPLICATION
	IN ROLE "MyAppDevelopers"
	PASSWORD '#UPASS#';

	COMMENT ON ROLE "MyAppUser"
		IS 'PostgreSQL user for My App general use';

Nothing too fancy there. I'm creating my group/users and putting the users into the group. It's the next "step" of creating the database and schemata where I'm trying to fine-tune the access levels. I may be going a bit overboard or I may be missing/overlooking something, but here's how I have it now:

--
-- Name: myappdb; Type: DATABASE; Owner: MyAppDevelopers;
--
CREATE DATABASE myappdb WITH
    OWNER = "MyAppDevelopers"
    ENCODING = 'UTF8'
    LC_COLLATE = 'English_United States.1252'
    LC_CTYPE = 'English_United States.1252'
    TABLESPACE = pg_default
    CONNECTION LIMIT = -1;

COMMENT ON DATABASE myappdb
    IS 'Data and configuration information storage for My App';

GRANT ALL PRIVILEGES ON DATABASE myappdb TO "MyAppDevelopers";

REVOKE ALL PRIVILEGES ON DATABASE myappdb FROM public;

--
-- Name: AppData; Type: SCHEMA; Owner: MyAppDevelopers;
--
CREATE SCHEMA "AppData"
	AUTHORIZATION "MyAppDevelopers";

ALTER DEFAULT PRIVILEGES
	FOR ROLE "MyAppDevelopers"
	IN SCHEMA "AppData"
	REVOKE ALL PRIVILEGES ON TABLES FROM public;

ALTER DEFAULT PRIVILEGES
	FOR ROLE "MyAppDevelopers"
	IN SCHEMA "AppData"
	REVOKE ALL PRIVILEGES ON SEQUENCES FROM public;

ALTER DEFAULT PRIVILEGES
	FOR ROLE "MyAppDevelopers"
	IN SCHEMA "AppData"
	REVOKE ALL PRIVILEGES ON ROUTINES FROM public;

ALTER DEFAULT PRIVILEGES
	FOR ROLE "MyAppDevelopers"
	IN SCHEMA "AppData"
	REVOKE ALL PRIVILEGES ON TYPES FROM public;

ALTER DEFAULT PRIVILEGES
	FOR ROLE "MyAppDevelopers"
	REVOKE ALL PRIVILEGES ON SCHEMAS FROM public;

ALTER DEFAULT PRIVILEGES
	FOR ROLE "MyAppDevelopers"
	IN SCHEMA "AppData"
	GRANT ALL PRIVILEGES ON TABLES TO "MyAppDevelopers";

ALTER DEFAULT PRIVILEGES
	FOR ROLE "MyAppDevelopers"
	IN SCHEMA "AppData"
	GRANT ALL PRIVILEGES ON SEQUENCES TO "MyAppDevelopers";

ALTER DEFAULT PRIVILEGES
	FOR ROLE "MyAppDevelopers"
	IN SCHEMA "AppData"
	GRANT ALL PRIVILEGES ON ROUTINES TO "MyAppDevelopers";

ALTER DEFAULT PRIVILEGES
	FOR ROLE "MyAppDevelopers"
	IN SCHEMA "AppData"
	GRANT ALL PRIVILEGES ON TYPES TO "MyAppDevelopers";

ALTER DEFAULT PRIVILEGES
	FOR ROLE "MyAppDevelopers"
	GRANT ALL PRIVILEGES ON SCHEMAS TO "MyAppDevelopers";

REVOKE ALL PRIVILEGES ON SCHEMA "AppData" FROM public;

--
-- Name: AppSettings; Type: SCHEMA; Owner: MyAppDevelopers;
--
CREATE SCHEMA "AppSettings"
	AUTHORIZATION "MyAppDevelopers";

ALTER DEFAULT PRIVILEGES
	FOR ROLE "MyAppDevelopers"
	IN SCHEMA "AppSettings"
	REVOKE ALL PRIVILEGES ON TABLES FROM public;

ALTER DEFAULT PRIVILEGES
	FOR ROLE "MyAppDevelopers"
	IN SCHEMA "AppSettings"
	REVOKE ALL PRIVILEGES ON SEQUENCES FROM public;

ALTER DEFAULT PRIVILEGES
	FOR ROLE "MyAppDevelopers"
	IN SCHEMA "AppSettings"
	REVOKE ALL PRIVILEGES ON ROUTINES FROM public;

ALTER DEFAULT PRIVILEGES
	FOR ROLE "MyAppDevelopers"
	IN SCHEMA "AppSettings"
	REVOKE ALL PRIVILEGES ON TYPES FROM public;

ALTER DEFAULT PRIVILEGES
	FOR ROLE "MyAppDevelopers"
	REVOKE ALL PRIVILEGES ON SCHEMAS FROM public;

ALTER DEFAULT PRIVILEGES
	FOR ROLE "MyAppDevelopers"
	IN SCHEMA "AppSettings"
	GRANT ALL PRIVILEGES ON TABLES TO "MyAppDevelopers";

ALTER DEFAULT PRIVILEGES
	FOR ROLE "MyAppDevelopers"
	IN SCHEMA "AppSettings"
	GRANT ALL PRIVILEGES ON SEQUENCES TO "MyAppDevelopers";

ALTER DEFAULT PRIVILEGES
	FOR ROLE "MyAppDevelopers"
	IN SCHEMA "AppSettings"
	GRANT ALL PRIVILEGES ON ROUTINES TO "MyAppDevelopers";

ALTER DEFAULT PRIVILEGES
	FOR ROLE "MyAppDevelopers"
	IN SCHEMA "AppSettings"
	GRANT ALL PRIVILEGES ON TYPES TO "MyAppDevelopers";

ALTER DEFAULT PRIVILEGES
	FOR ROLE "MyAppDevelopers"
	GRANT ALL PRIVILEGES ON SCHEMAS TO "MyAppDevelopers";

REVOKE ALL PRIVILEGES ON SCHEMA "AppSettings" FROM public;

All of the tables, views, functions, sequences, etc. will be created after logging out of the maintenance/administrator user and then back in using the MyAppAdmin user created above. There are other things I'd like to do from a setup perspective as a part of this script (*like implementing some sort of schema versioning*), but they're outside of the scope of the basic user/permissions setup in this question, so I'll save those for later. So, I guess my question(s) to all you wonderful DBA's out there is, am I SQL-ing right here? Am I missing something obvious that might conflict with my stated goals? Is there a "better"/more efficient way to get this done? I'd appreciate any feedback or suggestions.

I have a SQL Server 2008 R2 server with several instances installed. Is there a way to add a new instance and have it be to the same build as the existing (and updated / patched) instances?

I have installed PostgreSQL 12 from https://www.2ndquadrant.com/en/blog/pginstaller-install-postgresql/ . and put \C:\...\PostgreSQL\12\bin in the PATH. In an admin powershell I execute psql.exe -U postgres and enter the password I chose in the installation wizard. Now I'm in a shell. I want to create a database so I run createdb but it seems the database is not created:

postgres-# \l
                                          List of databases
   Name    |  Owner   | Encoding |       Collate       |        Ctype        |   Access privileges
-----------+----------+----------+---------------------+---------------------+-----------------------
 postgres  | postgres | UTF8     | German_Germany.1252 | German_Germany.1252 |
 template0 | postgres | UTF8     | German_Germany.1252 | German_Germany.1252 | =c/postgres          +
           |          |          |                     |                     | postgres=CTc/postgres
 template1 | postgres | UTF8     | German_Germany.1252 | German_Germany.1252 | =c/postgres          +
           |          |          |                     |                     | postgres=CTc/postgres
(3 rows)


postgres-# createdb demo
postgres-# absolute nonsense
postgres-# \l
                                          List of databases
   Name    |  Owner   | Encoding |       Collate       |        Ctype        |   Access privileges
-----------+----------+----------+---------------------+---------------------+-----------------------
 postgres  | postgres | UTF8     | German_Germany.1252 | German_Germany.1252 |
 template0 | postgres | UTF8     | German_Germany.1252 | German_Germany.1252 | =c/postgres          +
           |          |          |                     |                     | postgres=CTc/postgres
 template1 | postgres | UTF8     | German_Germany.1252 | German_Germany.1252 | =c/postgres          +
           |          |          |                     |                     | postgres=CTc/postgres
(3 rows)

I assume that my command createdb demo fails without error response as the intentionally wrong next command absolute nonsense fails as well. But I don't know how else to create a db, and moreover I'd like to know why this doesn't work and how to debug this.

I have a "Microsoft SQL Server Express 2008 R2 SP1" installation on a machine without the "Advanced Services". Now I want to install the "Full-text Search", so I downloaded the setup "SQLEXPRADV_x64_DEU.exe". The problem is, if I start the setup, select my existing sql-instance and go further to the feature-selection menu, I don't see the "Advanced Services". I just see the already installed features. Here's a screenshot (in german): I did the installation of the "Full-text Search" on about 20 different machines with existing sql-instances without problems. But on this machine, I don't know what's the problem. Hope somebody can help me! Thanks in advance!

I am running SQL Server 2017 Standard CU 5 in a failover cluster with two nodes (single instance cluster). I have followed these two manuals to deactivate CEIP aka spyware features: - The CEIP service is disabled and stopped, - the CEIP role removed from the cluster - and all registry entries regarding CustomerFeedback and EnableErrorReporting are set to 0. However I still get the message "Software Usage Metrics is enabled." in SQL Server error logs after a service restart. Additionally there are frequent errors from ESENT like the following in my windows event log: There is a MS Knowledge Base article for this problem. However it is for SQL Server 2012. It says that this error is related to the "Software Usage Metrics feature". I already followed the advice to grant permissions for the SQL Server service account. However the error message keeps appearing and I don't want Microsoft to collect data anyway. Here are my questions: 1. Is that the same feature as the CEIP stuff or something else? 2. How do I deactivate Software Usage Metrics correctly?

I recently installed a new Sql Server 2016 and selected the root of drive N:\ for transaction logs and drive Z:\ for tempdb. In the end the server was succesfully installed and running. But it was not possible to access the drives N or Z anymore. I suspected Sql Server to expect a folder instead of the whole drive and to change the security settings / permissions on this folder - which in my case was performed on the drive's root and may have caused the symptoms On the other hand I am pretty sure that I have already sees Sql Server installations using with the root of drives. Now I wonder if there is a bug in the setup or if it was my fault to configure it that way. And how this can be fixed? Meanwhile IT has modified and opened access to the drives for me, so I can access them now, but Sql Server Service actually is stopped. Do I have to reinstall the sql server or do I have to change all the database's path / log path to a subfolder that has to be created? Does anyone know what went wrong here?

adcfgclone.pl dbconfig fails when trying to configure the database to use logical host names. Unable to make database connection, error in ApplyDatabase.log " Exception occurred: java.sql.SQLRecoverableException: IO Error: The Network Adapter could not establish the connection Connection could not be obtained; returning null" Database version: 12.1.0.2 Oracle E-Business Suit version : 12.1.3 Steps performed: 1. Adpreclone.pl run on apps tier and two database node (2 node rac database) 2. Created context file on the first database node to use logical hostname. 3. adcfgclone.pl dbconfig being run to configure the database to use logical name. Error at this step.

I've recently tried to install Microsoft SQL Server setup.exe using well tried syntax I used before, but run into error the because of '=' sign in my user password. See sample command below: setup /QUIET /ACTION=REBUILDDATABASE /INSTANCENAME=MSSQLSERVER /SQLSYSADMINACCOUNTS=Domain\User /SAPWD=Pass=word Is there a way to screen equal sign or somehow specify password for SAPWD switch so that it has equal sign in it bud not causing error?

I'm trying to set up oracle-xe on my Linux machine. I just need an environment to play with Oracle SQL; this is not for production. When I try to start SQLPLUS I keep getting one of the following errors: ORA-12541: TNS:no listener ORA-28547: connection to server failed, probable Oracle Net admin error There are quite a few posts regarding similar problems, but even after trying many different "solutions" I'm still lost. I'm probably doing something horribly wrong. See the following outputs: [oracle@roshan ~]$ whoami oracle [oracle@roshan ~]$ pwd /usr/lib/oracle [oracle@roshan ~]$ echo $ORACLE_HOME /usr/lib/oracle/product/11.2.0/xe [oracle@roshan ~]$ echo $ORACLE_SID PLSExtProc [oracle@roshan ~]$ cat product/11.2.0/xe/network/admin/tnsnames.ora # tnsnames.ora Network Configuration File: XE = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = XE) ) ) EXTPROC_CONNECTION_DATA = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC_FOR_XE)) ) (CONNECT_DATA = (SID = PLSExtProc) (PRESENTATION = RO) ) ) SQL_AUTHENTICATION_SERVICES = (NONE) [oracle@roshan ~]$ product/11.2.0/xe/bin/lsnrctl start LSNRCTL for Linux: Version 11.2.0.2.0 - Production on 22-OCT-2017 12:24:03 Copyright (c) 1991, 2011, Oracle. All rights reserved. TNS-01106: Listener using listener name LISTENER has already been started [oracle@roshan ~]$ product/11.2.0/xe/bin/lsnrctl status LSNRCTL for Linux: Version 11.2.0.2.0 - Production on 22-OCT-2017 12:24:07 Copyright (c) 1991, 2011, Oracle. All rights reserved. Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC_FOR_XE))) STATUS of the LISTENER ------------------------ Alias LISTENER Version TNSLSNR for Linux: Version 11.2.0.2.0 - Production Start Date 22-OCT-2017 12:21:18 Uptime 0 days 0 hr. 2 min. 48 sec Trace Level off Security ON: Local OS Authentication SNMP OFF Default Service XE Listener Parameter File /usr/lib/oracle/product/11.2.0/xe/network/admin/listener.ora Listener Log File /usr/lib/oracle/diag/tnslsnr/roshan/listener/alert/log.xml Listening Endpoints Summary... (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC_FOR_XE))) (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=roshan.localdomain)(PORT=1521))) Services Summary... Service "PLSExtProc" has 1 instance(s). Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service... Service "XE" has 1 instance(s). Instance "XE", status READY, has 1 handler(s) for this service... The command completed successfully [oracle@roshan ~]$ sqlplus SYSTEM/foobar@localhost:8080/PLSExtProc SQL*Plus: Release 12.2.0.1.0 Production on Sun Oct 22 12:24:14 2017 Copyright (c) 1982, 2016, Oracle. All rights reserved. ERROR: ORA-12541: TNS:no listener Enter user-name: % [oracle@roshan ~]$ sqlplus SYSTEM/foobar@localhost:1521/PLSExtProc SQL*Plus: Release 12.2.0.1.0 Production on Sun Oct 22 12:24:27 2017 Copyright (c) 1982, 2016, Oracle. All rights reserved. ERROR: ORA-28547: connection to server failed, probable Oracle Net admin error Enter user-name: % [oracle@roshan ~]$ su Password: [root@roshan oracle]# /etc/rc.d/oracle-xe status LSNRCTL for Linux: Version 11.2.0.2.0 - Production on 22-OCT-2017 12:32:06 Copyright (c) 1991, 2011, Oracle. All rights reserved. Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC_FOR_XE))) STATUS of the LISTENER ------------------------ Alias LISTENER Version TNSLSNR for Linux: Version 11.2.0.2.0 - Production Start Date 22-OCT-2017 12:21:18 Uptime 0 days 0 hr. 10 min. 47 sec Trace Level off Security ON: Local OS Authentication SNMP OFF Default Service XE Listener Parameter File /usr/lib/oracle/product/11.2.0/xe/network/admin/listener.ora Listener Log File /usr/lib/oracle/diag/tnslsnr/roshan/listener/alert/log.xml Listening Endpoints Summary... (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC_FOR_XE))) (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=roshan.localdomain)(PORT=1521))) Services Summary... Service "PLSExtProc" has 1 instance(s). Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service... Service "XE" has 1 instance(s). Instance "XE", status READY, has 1 handler(s) for this service... The command completed successfully Does any of these look very wrong?

What is the best way to re-install a SQL Server that was installed using a wrong language without losing any configuration? - Should I install a second instance parallel to the default instance - here I do not know if this is anyhow possible at all if using a different language? - Or should I install a second installation of Sql Server (as if it were two different Versions)? - Alternatively I could of course uninstall the old and install a new Sql Server using the correct language. Independent of the way to go, as you can imagine, I definitely want to avoid doing all the maintenance work for creation of Logins, Users, Permissions, Alerts, Operators, Jobs etc. again. Is there a good approach to achieve this?

When I install SQL Server 2008 R2, I get this message: > Previous release of Microsoft Visual Studio 2008 -- Failed ([screen shot](https://i.sstatic.net/SD0nA.jpg)) I can't proceed to the next step. How can I fix this?

I am trying to install **SQL Server 2012 Enterprise** with SQL Server **Data Tools** included. I understand that SQL Server Data Tools is part of what was formerly known as BIDS. The installation for SQL Server 2012 prompts me for the **ms_setup.msi** installation file from Visual Studio **2010**. However, I am using Visual Studio **2012** currently only. The equivalent file in VS 2012 is called vs_professionalcore.msi and is located in Visual_Studio2012_Pro\packages\professionalcore\Setup\. **How can I install SQL Server 2012 with Data Tools having only Visual Studio 2012 given the setup?** Is there a download or registry entry I need to make? Thanks for any pointers.

I am using following command line to install SQL Server 2008 R2 but its not installing. Also, I am not getting any error or log in summary.txt. > "D:\SQLEXPR32_x86_ENU (1).exe" /q /ACTION= Install /FEATURES=SQL > /INSTANCENAME=nvt /SECURITYMODE=SQL /sapwd=abc > /IACCEPTSQLSERVERLICENSETERMS

I have the latest versions of PostgreSQL and its GUI-frontend, pgAdmin, installed. When I try to register a new server a fatal error appears when pgAdmin tries to connect to the newly created server - **password authentication failed for user "postgres"**. I'm using a non-default port which was properly updated in the postgresql.conf file so I don't believe that is causing problems (restarted postgres too, as it so politely asks you to). postgres processes are running properly: Here you can examine the configuration settings I am using to register the server: I've tried a few passwords, including my root password but none of them appear to be working. Maybe the user has to be created separately? This is the first time I'm encountering anything besides SQL Server or Access so please bear with me if the question and its possible solution seem far too trivial. I'm running Linux Mint 15, 32-bit. I will provided additional information, if needed of course.

I'm installing a new instance of MS SQL. There is a step asking to specify instance root. The current DBA is off but I want to follow his logic / way of doing things. The installer lists the existing instances but does not specify the configured paths. A quick google search doesn't reveal anything useful either. The question is in the title.