We have an Excel file from which it retrieves information from a SQL Server DB.
Here is a snippet of the code:
Provider=SQLOLEDB.1;Persist Security Info=True;User ID=mjone;Initial Catalog=pff_db;Data Source=....
My question is that for mjone, how is he able to get connected to the SQL Server DB? I am looking at the SQL Server Management Studio and do not see any mjone used.
Check these:
Check the users under `pff_db`
Check global SQL Server Users
Check if that user exists in the server (Windows)
Related
I have a problem on connecting microstrategy to a local database:
I'm unable to resolve this error, though I have tried everything in ODBC origins, and tried various drivers.
The server name is correct (SQLExpress2017)
If anyone knows how to resolve this issue, please help.
How to connect Micro Strategy 10 to SQL Server
We cannot connect the SQL SERVER 2017 through local by making the sql server dynamic access by allowing TCP/IP using(sql configuration manager)
NOTE
1)Within your network your system be accessible making dynamic sql server
After create odbc in Microstrategy server.in creating ODBC password should be your sql server username and password and create database instance in microstrategy.using datawarehouse catalog fetch the table based upon the instance you created
My objective is to use the migration tool in SQL Developer to migrate 2 SQL Server databases to Oracle. I am attempting to connect to a SQL Server database at a remote location using Oracle SQL Developer 4.0.
I have installed jtds.1.3.0.jar per instructions, and get the SQL Server and Sybase tabs in the connection properties window.
I have entered the user, pw, hostname, port, and database name. When I try to Retrieve Database, or connect, I get the error message:
Status : Failure -Test failed: I/O Error: DB server closed connection.
The SQL Server DBA tells me her error logs contain the following error message:
Encryption is required to connect to this server but the client library does not support encryption; the connection has been closed. Please upgrade your client library. [CLIENT: (my computer's IP address)] Error: 17835, Severity: 20, State: 1.
When I look at SQL Server documentation about this error message, it talks about certificates and SQL Server Connection Manager. Some relevant information to show that I've covered the basics:
Using the same connection parameters, I am able to connect to the SQL Server database using Toad for SQL Server.
Using the same connection parameters, a DBA set up an Oracle Transparent Gateway, and I can connect to the SQL Server database using the gateway and a database link. (As far as I know, neither of these methods required a certificate to connect.)
Both of these use ODBC; SQL Developer uses jdbc with TCP/IP.
The DBA assures me TCP/IP connection is turned on for the SQL Server databases.
I have gone into the XML file where SQL Developer stores the connection string. It has the form jdbc:jtds:sqlserver://sql-xxx-xxx.mw.nos.xxx.com:1433/my_db, which looks correct. I have tweaked it by adding the instance name, but no difference. The database has a default instance name, anyway, so it shouldn't be necessary.
A co-worker has been able to connect to a local SQL Server database on the same machine where SQL Developer was running (both on his laptop).
As a workaround, I am also pursuing the possibility of installing SQL Server on a local workstation, and copying the databases there for processing, but I don't know if I can get approval. If you know another tool for migrating from SQL Server to Oracle, please also let me know.
Thanks in advance.
I have a remote windows server and SQL Server 2008 installed. How can I check the access log of SQL Server with the IP address that tried to access the DB?
I tried in SQL Server Management Studio -> Management->SQL Server Log. It doesn't show the IP address.
As far as I know, if you missed to set up login auditing, you can't.
By default, only failed logins are logged. You have to set your server instance to log both failed and successful logins.
You can find some details here
I am testing an application. In tableadapter configuration wizard, On server side:
While choosing data source, I chose Microsoft SQL Server Database File.
This gave the connection string as:
Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\Database1.mdf;Integrated Security=True;User Instance=True
Is this correct?
Any way this works in my desired way.
Then in SQL Server Mgmt Express, I attached the database to the instance of my SQL Server Express (to MyhomeServer\SQLExpress"
Now I want to use the same application on Client side (off course databse is stored in Data Directory of my application in Server Side) Now in tableadapter wizard, I choose Microsoft SQL Server Express. Is that correct?
I have done all configurations for remote connection etc. and also done the firewall settings. When I run this test on client side, it returns error:
Cannot open database "Database1.mdf" requested by the login. The login failed. Login failed for user 'MYHOMESERVER\Kh. Furqn'.
Why does it go to Kh. Furqan while I am giving it SQLExpress, where the DB is attached. My server is MyHomeServer\SQLExpress and connection is MyHomeServer\Kh. Furqan (Authentication is Windows Authentication, and no password for it)
Since you chose integrated security the program will try to log onto SQL Server with the current logged on user's credentials - 'MYHOMESERVER\Kh. Furqn'. So the first place I would check is make sure that you can log onto Sql Server Mgmt Studio (SSMS) Express with the windows logon option and logged into the server as Kh. Furqn. Let me know if that works.
Wade
I created a new login using Express Management Studio and SQL Server authentication. On create, the password changes to some long format automatically and I am not able to connect using the newly created user with the password I have set.
What do I have to do to let it use the same password that I set and not tamper with it ?
I think Frosco's comment is spot on. Sql Server is not changing the password that you entered, but SQL Server Management Studio (SSMS) is visually modifying the password and confirm password entry boxes to make it appear that the password is longer than what it is.
Have you tried creating the new SQL account, exiting SSMS and reconnecting to the SQL Server instance through SSMS using the newly created SQL Account & password? If this works then you know that you created the account properly and that the password is in fact correct.
As Frosco also said, if you are unable to connect to the SQL Server database remotely it most likely is due to the fact that SQL Server Express is not configured out of the box to accept remote connections.
This KB Article describes the steps you would take to enable remote connections. It is written towards SQL Server 2005, but I believe the same basic steps apply to SQL Server 2008.
http://support.microsoft.com/default.aspx?scid=kb;EN-US;914277