connecting to sql server from classic asp - sql-server-2008

I have a sql server 2008R2 express running in windows authentication mode. I created a login and a user for a database in sql server based on a windows account. I can connect to sql server database via(run as the user) SSMS and browse my database just fine.
Now i am trying to connect via a 3rd party asp application
set loginDB = Server.CreateObject("ADODB.Connection")
'For Windows Server 2008 / SQL 2008 users, please use the following line for the DB connection
loginDB.Open "Provider=SQLNCLI10; Server=(local)\SQLServerName; Database=dbname;Uid="myuser" Pwd="pwd""
I am getting an error saying login failed for user myuser
Also the site is running on an app pool which i have set it to run as the windows user myuser.
Where am i going wrong???
Thanks.

If you are passing username and password that's SQL Server Authentication not windows, so if it's authentication mode is Windows only, it won't have it.
Take them out and replace with Integrated Security = SSPI

Related

Visual Studio Code mssql extention: SQL Server (mssql) - Unable to connect to server

I'm trying for the first time to get my project to run in Visual Studio Code. This includes a MySQL database. So I've installed the SQL Server (mssql) extension version 1.7.1. I follow the instructions here: https://learn.microsoft.com/en-us/sql/visual-studio-code/sql-server-develop-use-vscode?view=sql-server-ver15
I get to the section "Connect to SQL Server" and enter:
servername: localhost
db name: c3
Authentication type: Integrated
At the end of the section it should connect with the server but instead I get two errors:
mssql: Error "Unable to connect using the connection information
provided. Retry profile creation?"
mssql: Error 2: A network-related or instance-specific error occurred
while establishing a connection to SQL Server. The server was not
found or was not accessible. Verify that the instance name is correct
and that SQL Server is configured to allow remote connections.
(provider: Named Pipes Provider, error: 40 - Could not open a
connection to SQL Server)
Does anyone see what is going wrong here?
I've re-installed the extension but with the same result.
A MySQL db and Microsoft SQL Server db are two different things.
It seems that there's no SQL Server installed? You might install the free SQL Server Express Version, create the database in there and then connect from Visual Studio Code.
You have to install the database server yourself as VS Code is just a client. You might also use somekind of hosted offers (many webhosters offer a mysql server with self service installation, or use a cloud based database server). Yout can also use a local database (e.g. SqlLite) which is file based and doesn't need a special installation.
You should do the following
install SQL server in your machine and create Database here
Create a login and a database user here
If you are Using VS code install SQL Server (mssql) open new
connection, follow the prompts to specify the properties for the new
connection profile
If you want to login to your server to make sure of your data
sqlcmd -S localhost -U SA -P '<YourPassword>'

SQL Server SA Password for SQL Server Authentication?

I am working on SQL Server 2008 and currently I am using my local server with windows authentication. Can i set SA password for SQL Server Authentication? What are the steps and also I want to know what is the difference between Windows and SQL Server Authentication?
Window Authentication: If you are authorized user to window and you have proper right to access sql server. you are all done to access sql server, you don't need any username/password to access sql server.
SQL Server Authentication: You need to create new user to access sql server (a part from window user). You need username & password of newly created user to access sql server.
You can create new SQL Server Authentication user by: Object Explorer >> Security >> Login >> New Login. Again, you need required right for the window user through which currently you are accessing sql server.

Connection to SQL Server 2008: error 18452

I have a problem with connection to SQL Server 2008.
My problem is all simple user can't connect to SQL Server 2008 but just the admin in subdomain only who can connected.
I test the connection with these steps:
control panel / set up odbc
system DNS / I choose SQL Server
click on the bottom Add
in the Name=test, and the server = I choose SQLSERVER
When I clicked Next bottom I have error 18452.
Connection failed: SQLState: '28000'
SQL Server Error: 18452
[Microsoft][ODBC SQL Server Driver][SQL Server] connection failed.
SQL Server Error: 18452
Login failed for user ". The user is not associated with a trusted SQL
Server connection.
You should create new DSN with changed Authentication Mode from Windows Authentication Mode to SQL Server Authentication. Then specify login and pass for connection. This login should be added on SQL too.
I were trying to do the same, saw a lot of videos trying to accomplish the add of the DSN but this was my solution.
I'm running Windows Server 2016:
I ran the ODBC 64bit -> System DSN tab -> Add button
Then I selected SQL Server, since i had SQL Server Management Studio 17.
I putted a Name and the fact that is really important: Write the SQL Server you know you have connection to on the Server field.
Be sure you had configured the Security on Server authentication for SQL Server and Windows Authentication mode and then write the user you know that have access to that Data Base.
Last step: you click next after putting the info of the user that have acces to the SQL Server and the connection will pass.
Hope this help someone.

Connect to sql server with management studio

I have a sql server hosted on go daddy that I simply am unable to connect to using Visual Web Developer 2010 Express or Microsoft SQL Server Management Studio.
Cannot connect to RBSAssetTracker.db.2574383.hostedresource.com.
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 67)
Am I missing something? This seems like it should be relatively simple to accomplish this.
first check whether you can ping the database server then check following
Step 1) Make sure SQL SERVER is up and the instance you try to connect is running.
Step 2) Your system Firewall should not block SQL Server port.
Step 3) Go to Computer Management >> Service and Application >> SQL Server 2005 Configuration >> Network Configuration
Enable TCP/IP protocol. Make sure that SQL SERVER port is by Default 1433.
Step 4) Now follow this KB Article of MSDN depending on your server : http://support.microsoft.com/default.aspx?scid=kb;EN-US;914277
open your godaddy account,
click launch under your webhosting menu,
click on SQL server database
click actions-->details and watch for the 'hostname'
it will be like : databasename.db.99999999.hostedresource.com
copy and paste that thing to 'Server name' while logging to your management studio
Enter your godaddy sql-server database username and password to login in management studio. It should work right.

Cannot create sql server database user correctly

I'm trying to create a user in a SQL Server database with SQL authentication. That's what I did:
Created database named testDb (with default parameters)
ran script
CREATE LOGIN test
WITH PASSWORD = 'test';
USE testDb;
CREATE USER test FOR LOGIN test;
GO
Ensured user test appeared in Databases\testDb\Security (in Management Studio)
Tried to connect to the server with Management Studio using user test
Got 18456 error.
I'm using SQL Server 2008 Developer Edition. The OS is Windows 7 Ultimate. What am I doing wrong?
By default SQL Server logins are disabled.
You need to right click the instance in SSMS object Explorer then from the "Properties" dialogue, Security Tab enable "SQL Server and Windows Authentication mode".
This requires a restart of the SQL Server service to take effect,