connect to MSSQL2005 via ODBC

Installed SQL2005, connect via (the new) SQL Nativ Client ODBC Vers. 2005.90.1399.00 works, just as (the old) SQL Server ODBC-Driver 2000.85.1117.00. Works fine.
But from an other machine -there is no client installed - using driver 2000.85.1117.00 I get the message "Server dosn't exist or access denied"
How I can connect ? It is due to the fact of .NET FRAMEWORK 2 ?
Thanks!Sounds like the 'other' machine is your first network client - check your enabled protocols with SQL Server Configuration Manager.

Also, check your connection details include the instance name if necessary.

Also, what are the OS levels and authentication method?|||Hi, Mulhall. Indeed, it's the first network client W2K, connections to other sql2000 servers are o.k., to SQL2005 tried using TCP/IP-Protocol, tried Named Pipes and all others. Using the standard instance, no named, using SQL-authentication such as win-authentication, tried connection by server-name and by IP-Adress. OS-Ping works normaly.|||Have you verified using the Surface Area Configuration tool that remote connections are enabled?

Thanks
Laurentiu|||Thanks Laurentiu, upon configuration Surface Area Conf.Tool the connection works. I did not know this feature

Connect to database without showing the "Connect to Server" dialog box?

Is it possible to configure the SQL Server Management Studio to behave like good old Enterprise Manager, so that it automatically connects to my configured servers without showing the "Connect to Server" dialog box every time upon startup?

After successlessly searching Google and these forums, I still found no suitable answer to this question (maybe beside this one).

Thanks
Uwe

You ae right this is not possible, perhaps you can suggest that as a feature request on connect.microsoft.com ?

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de|||Done:

http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=180590

Thanks, Jens .|||You got my vote.

-Jens.|||Strange - they marked the ticket as "closed" and "solved", but no further comments.

Anyone knows what this actually means? IS it already present and I did not found it? Or will it be implemented in a further version?

Thanks
Uwe

Conflict with logins/usres when Importing databases

Hi,

We have imported several databases from an old SQL Server 2000 deployment in a SQL Server 2005 instance. After the installations we have check that the import doesn't create the logins associated with the users nad now it seems impossible to create "manually" the login. What should be do? Re-import the database after having created the login?

Thanks
You should still be able to create the login using CREATE LOGIN and then run the system proc
sp_change_users_login to map the existing users to the newly created login.

Reimporting the database will probably not work as the SIDs of the new logins will not match those of the old logins.

HTH.
|||Effectively, we have been able to create the login but we are unable to associate it to the user using the the "User Properties". The field "Login" appears empty and disabled, so there is no way to assign a user from this screen.

Reading your answer I understand that I can map the users to the newly created logins using the sp_change_users_login function. It's true? Could you send me a sample of use of this function? How should we execute it? (We are SQL Server newbies coming from Oracle world......)+

Thanks
|||

I assume you imported only your user-database probably using import wizard or something. Security information (users and logins) is stored in 'master' database in SQL Server world. You have to transfer these information from your old database to new one.

Check this out.

How to transfer logins and passwords between instances of SQL Server

http://support.microsoft.com/kb/246133/en-us

|||sample:

sp_change_users_login 'AUTO_FIX', 'some_login'

|||Check the information in Books Online which will give you a full explanation of the options open to you:

http://msdn2.microsoft.com/en-us/library/ms174378.aspx

Essentially to map an existing user Bob to a new login of Bob you're looking at running:

sp_change_users_login 'Update_One', 'Bob', 'Bob';

Hope this helps;