Forum Moderators: phranque
please help
Open it up, click on 'alias' then 'add'.
Type something like 'local' for server alias, then type the NAME of your computer in the 'server name' box. Also, make sure that the TCP/IP is checked on the network libraries list on the left.
Once you have done that, open up enterprise manager.
Right click on 'SQL Server Group' on the left, then select 'New SQL Server Registration'.
On the list of available servers, you should see the one you just created via the client network utility. Click 'add' then 'next' then decide how you'd like to authenticate yourself on the SQL Server.
That should be all that's needed so you should be able to start playing with your databases.
If you also want to connect to a remote server, just do the same thing again but specify the details of the remote server in the client network utility.
Hope this helps :)
do i need IIS running on my pc.
I,m using win2k and my pc name is JWILLIS
If you did everything I said and you are get that error at that point, I'd imagine it's an authentication problem.
Are you logged into your PC as administrator? If so, I would imagine you'd need to register the sql server using 'windows account information'.
Are you doing it this way or are you trying to connect with a usernam/password?
When you installed SQL server, was there an option to set a username/password? I can't remember if there is or not.
when i go through the wizard i set it to use my logon windows username and password.
when i loaded sql it automatically detected my pc name. which is JWILLIS and that is it.
dont think i am logging on as aministrator. just as JWILIS
Operating System: Windows 2000 Server (previously running just the standard win2k)
Web Server: IIS5 installed from the Win2k CD.
Database: SQL2000
I don't think it matters whether you have any kind of web server installed as the database is seperate from it.
Do you have an SQL Server account with a web host anywhere that you can connect to first so you can get a feel of how it all works before trying to get your setup working locally?
Thanks
Secondly, using an Ent Edition or Dev Edition grade SQL install on anything less than a server grade OS will result in the setup complaining it can't install the full product on your current OS. However it *will* let you install a personal edition server if you try hard enough which unless you need to do *big things* with SQL Server this will suffice...
How to check if you have installed a sql server or not; (there are two methods, one is quick, one is not)
1) Do you have a new icon in your system tray? It looks like a gray PC tower with a white circle on the bottom corner - the circle indicates server state and it will be;
blank if the server state is unknown
red if its stopped
green if its running
2) Open your service control panel and look for a "SQL Server" entry, if you can see that line then it is installed. In the default state the SQL Server service will always start when you start the machine, but potentially if you see this line and it doesn't say started that would explain why you can't connect to the server.
If you have installed the server and it is failing to start you should be able to get a hint of why this is by viewing the event logs...
- Tony
When installing on my WIN2K machine I got this message! (MS SQL Server 2k server component is not supported on this operating system. Only client components will be available for installation)
I then selected to loads the clients tools upon installation.
It has installed now and i have the network utility and enterprise manager all under SQL when i got to start programs.
I do not have a little server tower in my my toolbox though
"Only client components will be available for installation"
You *need* the server components (specifically the SQL Server) in addition to the client components if you want to set up a SQL Server - if you dont install the server components then you wont be installing a SQL Server.
* Client tools are things like the enterprise manager, the query analyser, client network utility, profiler, data transformation services etc.
* Server components are things like the SQL Server service.
It is quite possible to install just the client tools without the server, as you are just installing the management tools without installing the sql server service.
As far as I am aware, the lack of the little icon in your tray means that you haven't installed a sql server - every sql server install I've completed with has installed the little tray icon unless I have instructed it otherwise.
Equally it has been my experience (and this is backed up by the admin guides) that the client network utility rarely needs to be used unless you want to change the protocols you use to connect, this in itself is something that happens rarely until you begin to start tweaking the server install.
Also if memory serves whenever you install sql client+server then the server is automatically added to your enterprise manager.
Solutions?
I'm pretty new to the 2k edition of SQL Server so I can't really suggest great work arounds for your problems except to say that there used to be a desktop edition of sql 7 but that product is now called the personal edition - it is essentially a cut down sql server + client tools which will install on a non-server OS.
- Tony
If you can find & install a sql server separately you can then add that server to the enterprise manager via the "add server" wizard. Also on the plus side SQL 2k client tools *are* backwards compatible so you could even try this with a v7 SQL Server if you really had to.
- Tony
lol
Got it working on my WIN98 pc. Its connected using my PC name and i have a server in the server pane with my pcs name on it and a green arrow. Well atleast i have made a connection. Thanks
The hardest part comes now. Figuring out how to work it all lol.
I installed a Desktop Engine which is on the CD. I think this helped somehow. Dont know but its worked.
like you've already found out, you can't install enterprise sql server2k on win2k pro. I use the trial version of sql server2k on my win2k machine for development. You can dl it from Microsofts web site. They allow you to reinstall it when your 120day trial licesnce expires and i'm guessing this is because you cannot install sql 2k server on a win2k pro machine you can only install the client tools. The only problem you will have using the trial version of sql server 2k is... there is a bug that occurs when you attempt to connect to another sql server 2k using enterprise manager and list the databases available. it will hang there and never come back. Your only option is to use enterprise sql server on a win2k/nt4 server machine or use Query analyzer. Other then that problem the trial version of sql server2k does the job for me. You can do everything that you can do with the full version it just tells you that your trial is over after 120 days, but again they have no problem with you reinstalling it as far as I know. Let me know what kind of progress you make.