How to find server name when installing SQL Server 2008 R2 - sql-server-2008-r2

I want to install SQL Server 2008 R2, so I need to put "server name", I tried my computer name but I got an exception, would you tell me how to find it please
and this is the exception ![enter image description here][2]

You can use .\SQLEXPRESS as the server name.
Check this link
EDIT:-
From the comments below posted by the user(thought that it is useful)
You can install SQL Server as an instance, which allows you to run
multiple environments on the same machine (ie. localhost\dev and
localhost\prod). If you install MSSQL Server Express, it defaults the
instance name to localhost\SQLEXPRESS

Use . as the server name. Or
From the server manager: Administration tools > Server Manager. You can get the computer name.

Use .\SQLEXPRESS
or
Use REVAN-PC\SQLEXPRESS
REVAN-PC is my System Name

Go to Start
write in search box: ODBC
Go to system DSN tab
click on Add...
select SQL server option and finish
Go to 3th box (server:) and see your server!

Try using (local) as server name. I had the same problem and after few attempts of connecting,(local) just came by default in the server name field.

Related

Unable to create connection in Oracle SQL developer . IO error

I cannot add a connection in oracle SQL developer installed.
The error I am getting is:
IO Error :The network adapter could not establish connection.
Also can anyone help me as to what user name and password it is asking?
Is there anything else I need to install.
SQL Developer is a tool which enables you to connect to the database - let's presume an Oracle one. Did you install it? If not, is there any available on the network? If not, you'll have to do that first (i.e. install a database - 11g Express Edition might be your choice, download it here), and then let SQL Developer connect to it.
As of username and password you'd use: database owner is SYS, but - you shouldn't use it for coding training - you'd rather create a new user, or unlock one of pre-installed; unless I'm wrong, 11gXE contains the HR schema (Human Resources). In order to unlock it, establish a connection to the previously mentioned SYS user (remember which password you choose for it during the installation process) and choose the SYSDBA role. Then unlock the HR user and modify its password by issuing the following statements:
alter user hr account unlock;
alter user hr identified by hr;
Now create a new connection to HR user (this time choose the "default" role); you should be able to see its tables, run queries, etc.
Make sure your oracle database is up and running.. if you are using docker you need to restart the oracle docker image in this case.
I had similar issue then i tried to restart the oracle using
docker-compose -f docker-image-oracle.yml -d up (in this case you might have a diff name).
or you can start docker image directly from cmd .
Make sure that your hostname, listener port, sid/service name, username/password are correct.
You can use lsnrctl status to get the port number.
There are four things that come to my mind:
Is your Oracle Database installed and running? If not, install it and make sure it works.
Have you entered the correct username and password? Have you entered the correct hostname and/ or port number? If hostname and port number are wrong, check the listener.ora file (if you have the permission). Alternatively, you can look into the tnsnames.ora file.
Maybe your listener is not working after all. With the command "C:> lsnrctl status" (on cmd), you can check, if the listener works. If it doesn't, run the command "C:> lsnrctl start".
Are you using the right URL?
The following link may help you:
https://community.oracle.com/tech/welcome/discussion/2547624/io-error-the-network-adapter-could-not-establish-the-connection

Unable to install SQL Server 2008 R2 Express

When I try to install SQL Server 2008 R2 Express, I get the following message :
The feature you are trying to use is on a network resource that is unavailable
Click ok to try again or enter an alternate path to a folder containing the installation package 'sqlncli_x64.msi' in the below box
I'm unable to find a way to solve this problem. Can you help me ?
For me this got fixed by -
Going to registry editor (windows+R > regedit)
Navigate to HKEY_LOCAL_MACHINE > SOFTWARE > Classes > Installer > Products
Goto each key listed under Products and delete all keys related to SQL Server (or the keys you think are specific to your error). This can be done by clicking on the key folder and reading the ProductName details in right pane (delete only the keys that contain keywords like SQL Server).
Once step 3 is complete, restart your machine and try again.

impact of sqlserver Name change on production database

I working on Creating a replication Between sqlserver on a non-trusted domain.But i have come to realize that i can only use the servername instead of the ip address of my server.I tried using the current server name i got from the sysadmin.But still connecting with the servername still display the same error:
sqlserver replication requires the actual servername to make connection
Connection throught a server alias,IP address, any other alternate are not supported
Specify the actual server name,'WIN-2JQ9ZRN3T'.(Replication.Utitilies).
I ran a script to show my server name:
Select ##SERVERNAME
The result was:WIN-2JQ9ZRN3T.This is very strange for me.I cannot connect with name i got from my sysad throught management studio,but on remote desktop i can remote connection using that name.
Now i want to update my servername using this script i came across on the internet:
sp_dropserver old-server-name
go
sp_addserver real-server-name, LOCAL
go
But i don't know what the impact would be because my predecessor configure a linkserver on the same server.Please advise
You have proposed a good solution: you have to update the server name accordingly and restart SQL Server, otherwise you'll not be able to use replication.
On the other hand, please check the replication component is installed, this will save you to make another restart.
Regarding your concern with linked servers, please run
SP_LINKEDSERVERS
and check if old server name appears in SRV_DATASOURCE column.
Another option could be to setup a sql server alias:
http://www.mssqltips.com/sqlservertip/1620/how-to-setup-and-use-a-sql-server-alias

SQL Server Agent gives- Remote procedure call failed (0x800706be)

Does Anyone knows the solution to this problem m not being able to run the SQL Server Services.
Solution: Install SQL Server 2008 R2 SP2, restart, open SQL Server Configuration Manager and ALL is good.
Source: Frozen bytes
No need to re-install or update your SQL Server 2008 R2 instance. I got the same error and it get resolved by simply starting the MSSQLSERVER standard service.
How to start this service:
Open Administrative Tasks > Services > Select Standard services tab > start SQL Server Agent(MSSQLSERVER) service and you are good to go.
With all due respect, "Right click on configuration manager and run as administrator" is a bogus answer. I also have this problem with the following series of events: I download the Windows Azure SDK from here: http://www.windowsazure.com/en-us/develop/downloads/, which installs SQL 2012 express; immediate I try to run SQL Server Configuration Manager, and the installation of SQL 2012 has broken it such that I get the "remote procedure call failed". That is true even if I "run as administrator". Microsoft says they can't reproduce this, but I've contacted them again because I've now reproduced this twice. And, if there's any doubt: un-installing SQL 2012 causes the problem to go away, and the configuration manager works again. I blogged about it here: http://dbarrowstechblog.blogspot.com/2012/09/the-remote-procedure-call-failed.html ; haven't solved it yet.
This error occurs only after I have installed the Microsoft Visual Studio 2012 setup in my work machine.
Since it is being a WMI error, I recompiled the MOF file –> mofcomp.exe "C:\Program Files (x86)\Microsoft SQL Server\100\Shared\sqlmgmproviderxpsp2up.mof"
I also un-registered and re-registered the sql provider DLL –> regsvr32 "C:\Program Files (x86)\Microsoft SQL Server\100\Shared\sqlmgmprovider.dll" but issue not resolved.
Solution:
I have applied SQL Server 2008 R2 SP2 on my SQL 2008 R2 instance and that fixed the issue with Sql Server Configuration Manager. You can download setup from here... http://www.microsoft.com/en-us/download/details.aspx?id=30437 .
Ok, Stop this.
Is this a new Installation?
Open SSMS in Integrated security Mode
Right click on server name in Object explorer tree at the left
Select properties -> Then choose the "Security" page at left
Under Server Authentication, select "SQL Server and Windows Authentication mode"
Click OK
Exit SSMS completely
Open "SQL Server Configuration Manager" (in Configuration menu under the "Microsoft SQL Server 2008 R2" menu item from start menu
Select you instance on SQLExpress and restart the instance of the server (but this is ok for non express too)
Exit SSCM - and to verify open SSMS again, but with "SQL Server Authentication" selected in the Authentication type dropdown - put in your SQL user ID and password.
installing the SP3 on SQL server 2008 worked for me..so give it try
Thanks!! dont forget to vote up if this helps you

what driver to use when connecting to Oracle 10 with IBM RAD / Eclipse DTP?

I'm using IBM RAD 7.5.5 (which is basically eclipse 3.4 (ganymede) + plugins).
I'm trying to create a connection to Oracle 10 using the "Data Source Explorer" view.
When I create a new connection for Oracle, there are three "driver" options:
"Oracle 10 - Oracle OCI Driver Default"
"Oracle 10 - Oracle Thin Driver Default"
"Oracle 10 - Other Driver Default"
1 & 2 don't work for me because I need to connect to the db using a "Service Name", not an "SID". The dialog box does not give me the option of specifying a Service Name, and it does not allow me to manually specify the connection URL. (Service Name has a different URL syntax, uses a '\' instead of a ':", like so ...
With SID: jdbc:oracle:oci:#localhost:1521:the_sid
With Service Name: jdbc:oracle:oci:#localhost:1521\the_sevrice_name
So ... I want to use option #3 which allows me to specify the URL manually. The problem is I add the driver file ojdbc14.jar to the JAR list, but it keeps telling me "Invalid JAR definition; driver list not defined".
Can anyone help? I'm really stuck on this. :(
Thanks,
Rob
FYI, at long last I found a solution to my problem.
While I was never able to establish the connection with the "Service Name" using Eclipse/DTP "Data Source Explorer", I was able to establish the connection with "Service Name" using SQL Developer. Once connected with SQL Developer, I did a ...
select sys_context ('userenv','instance_name') from dual;
... to determine the database's SID.
With the SID I was able to connect with option #1 and the driver contained in ojdbc14.jar.
Thanks all, Rob
If you are stuck with a more recent version of Oracle (e.g. Oracle 12) on a recent RAD or Eclipse installation you should try to do the following:
Download the Oracle 12 ojdbc7.jar. If you are on java6 you should download ojdbc6.jar
Create a new connection
Select Oracle 12 - Other Driver Default
Press the [...] dot, remove the default ojdbc6.jar and add the jar you downloaded before
Insert database name, the url (as jdbc:oracle:thin:#server:port/service ), the username and password, check the save password box if you wish.
Click Next and then Finish. Eclipse will try to test the connection, if the driver is still giving you problems then you need to force Eclipse (or RAD) to save the connection and you can fix it later.
Now you can fix the driver properties. This step is necessary to eventually be able to call the thin client in the jar.
In the database connection list choose the new connection you just created and press right button > properties
Choose Driver Properties
Click on the delta icon (the small triangle) near the Drivers combo box.
Open the Properties tab, then edit the properties as follow:
Catalog - USER
connection url - jdbc:oracle:thin:#server:port/service
Database Name - db
Driver Class - oracle.jdbc.driver.OracleDriver
Now your connection test should be succesful.