"About server-side SQL Server 2008 settings" makes other client machines accessible through an ODBC data source

Server System: Server 2003

Database: SQL Server 2005

On the server configured here, assuming that a new database named share is created in the database, we first "Create a new user"in security, named Tom, password 1234,

"Begin"SQL Server Authentication: set Password

Default database: Share

Language: Simple Chinese

Then switch to the Server Roles page: check all

Switch to User Mapping page: User mapped to this login: Tom database role membership: public

Security Object page does not make settings

Switch to Status page: Allow connection to database engine-allow; Login: Enabled. "End"

Note If you have previously created this user, and the property settings are inconsistent with the above, you need to remove this user from the security and security under Share database, and then create the new user

Server Configuration

Open Start-Program-sql Server 2008-Configuration Tools-SQL Server Configuration Manager

SQL Server Service--Start the SQL Server service and the SQL Server Browser service

SQL Server Network Configuration--sqlexpress Protocol-TCP/IP enable--IP Address tab write your own IP

SQL Native Client 10.0 configuration---TCP/IP enabled in clients protocol

--alias-Write your own IP "to write 1433 or none of the ports, after which the client computer ODBC data source needs to be set"

Back to SQL Server service-restart two services

Configuration of ODBC data sources:

Control Panel-Administrative Tools-Data source (ODBC)

User dsn: Add--sql server-name Tom, the server that was previously filled in with its own IP, next

SQL Server Authentication with user input login ID and password--the "Client Configuration" item is consistent with the port set above and the dynamic port tick is removed if fixed 1433

Test data Source-Success

"About server-side SQL Server 2008 settings" makes other client machines accessible through an ODBC data source