Setting up a SQL Server 2012 for various reasons. What are the differences vs a set up of a database, that are to be reached from remote. Well...there are some...There is a difference in terminology. And annoying default - but they are surely there for a reason - settings.
A very good thing is that there is no TNSNAMES.ORA...:-). The Windows authorization mechanism handles all of that. So when everything is in place the remote PC finds everything very smoothly, thru the network.
Every change of the settings are done in various parts of the SQL Server 2012 Manager-tool.
In SQL Server there is a concept of "USER" and (?) a "LOGIN". So...you couple the USER to a specific LOGIN.
CREATE USER myuser FOR LOGIN myuser;
You have to Enable TCP/IP protocol.
The annoying - imho - is the default setting that disables access from outside. So just find the Enable SQL Server & Windows Authorization.
From zero to an accessible database the time should not be more than 8-12 hours for a regular database knowledgeable person. But bare in mind that that is a straight forward installation.
10g (1) 11c (1) 11g (5) 12c (4) 3.0 (1) ApEx (4) Cloud (11) database (10) DBA (1) EBR (1) EC2 (2) education (3) EOUC (1) ExaData (1) F2F (1) Forms (7) java (1) language (2) memorabilia (2) Metalink vs MOS (4) multi-cultural (4) on-line communities (1) oracle (7) performance (5) projects (1) reciproke (1) Reports (2) RUP (1) sales (2) services (5) silence (1) SOA (3) SQL Server (3) standards (6) Sun (1) support (6) W8 (1) WebLogic Server (5)