Getting Started

[nickbungus]

Hello All

I am new to SQL server and I am trying to use it to further my programming skills.

A book I am using to program requests that the server 2000 Desktop engine is installed and offers some limited instructions.

I've tried to follow them but when installing MSDE I get a message saying that I have no SA PASSWORD. I found a solution to create a password and install and all seems fine but when I try to run a script from a command line I now get a message informing me that either the server doesnt exist or I do not have privilages.

I know that the server does exist so it must be the privilages. (bad programming giving an ambigous error).

I don't want to get bogged down with the complexities of SQL Server, please help???

Nick James

 

[Idokyoku2]

Did you load from command prompt? If so, did you try this:
SETUP INSTANCENAME="ANAMEOFYOURCHOICE" SECURITY=SQL SAPWD="APASSWORDOFYOURCHOICE"

 

[nickbungus]

I am starting the install from the command prompt.

The install seems fine, I have an icon informing me that my server is "Running - \\PC1 - MSSQL Server".

I am then typing this into the command prompt to run the script:
"osq -S PC1\VSdotNET2003 -E instnwnd.sql"

and I'm getting the following error:
"[DBMSLPCN]SQL Server does not exist or access denied.
[DBMSLPCN]ConnectionOpen (Connect() )."

I'm clueless. I hate command prompta - too much can go wrong!!

Any ideas anyone??

Nick

 

[vongrunt]

It is "osql", not "osq".

Either server instance PC1\VSdotNET2003 doesn't exist, or ... forgetabout -E for now, use explicit login/pass (-U and -P switches) instead.

MSDE has no query analyzer and you don't like prompt so... try some freeware GUI tools like Toad SS.

 

[SQLSister]

My first advice to you would be to spring for $50 or so and get the developer edition which will give you ENterprise Manager and Query Analyzer. It will be much easier to learn SQL Server if you have these client tools.

Questions about posting. See faq183-874
Click here to learn Ways to help with Tsunami Relief

 

[Idokyoku2]

I had something similar when loading SQL Server 7.0 on an older machine. I don't recall exactly what I did, but MS acknowledged it as being a problem. Apparently, when loading with a password from the command prompt, it doesn't save your password. It actually stores it as null, even when your sa.

Possible solution:
Using command prompt, navigate your way to OSQL and EXEC sp_changepassword 'null', 'Newsapwd'
or something similar?

I believe I found the solution on SQL Server 7.0 resource guide. Wish I could be of more assistance to you.

Have you tried simply loading a default instance with Windows Authentication?

David