How to set and use SQL Server Express 2005 after installation?

I have never used SQL Server, except that I did use MS Access, so after I downloading and installing the SQL Server Express 2005 ... I really do not know how to make it works!

1. Let say I would like to create a table at my local computer (1st) as a Server, how I do it (configuration)?

2. Then I have a second PC, as a client how I link to that table?

Might be they are 2 silly questions, but I would like to try out the new SQL Server Express and compare what are the better features with MS Access!

Thanks to any help

hi,

Anh Truong wrote:

I have never used SQL Server, except that I did use MS Access, so after I downloading and installing the SQL Server Express 2005 ... I really do not know how to make it works!

1. Let say I would like to create a table at my local computer (1st) as a Server, how I do it (configuration)?

SQLExpress, as SQL Server as well, is "just" a database engine (actually lot more than just that), but is not "an application" as well as you consider Access... actually, in Access world, the situation is the same as JET is the database engine and Access is the application intended to manage and interact with JET database(s)...

so, in Access, you just open "Access" and create your own database(s) and database's objects, where SQL Server/SQLExpress does not provide an ambient like that.. they feature other management tools... command line tools like SqlCMD.exe, or visual tools like SQL Server Management Studio (SQL Server Management Studio Express, for SQLExpress edition)... with these UI tools, you can visually interact with your instance, manage database(s) and database's object(s)... or, like in SqlCMD.exe, you can execute straigth Transact-SQL commands to perform both DDL and DML commands...

2. Then I have a second PC, as a client how I link to that table?

you are still "thingking" in term of JET/Access databases, a file based engine, where SQL Server/SQLExpress is a traditional client/server based architecture.. you do not create objects on a client... you always create them on the file system of the computer running the SQL Server instance, as you do not directly interact with the related files, but with the "server" only... it's up to the server to manage and interact with the underlying physical files..

as regard "remote" connections, you do not "link that tables"... you connect to the remote server, interacting with the desired database, querying relative objects like tables, procedures, views, .....

just remember SQLExpress installs by default disabling network protocols and remote connections... use SQL Server Configuration Manager to enable the desired network protocol, and Surface Area Configuration to enable remote connections over TCP/IP..
actually even managing the eventual FireWall comes to play, where you have to enable connections over the database engine used port (or binaries) and SQLBrowser port as well (UDP1434)..

SQLBrowser is an additional service used to resolve connections to Named Instances.. it listen on UDP1434 for incoming connections initiated by remote clients, it the queryies the Named Instance for it's used TCP/IP port and redirect the incoming connection to that port the instance is listening on..

regards