Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Hipogrito
Starting Member
4 Posts |
 Posted - 2005-10-10 : 07:48:48
|
Hello:First post here...We have a SQL Server 2000 running and we use an ODBC driver for passing data to Oracle in Linux. No probs here, everything works fine.So, we want to test SQLSS 2005 to see if our ODBC driver still works or not with this new system, with bad luck at the moment. So, I'm in this point that I don't know if I have to blame the driver or my installation of SQL Server 2005, so this is why I write here. Maybe some clever mind could help us.I have installed SQL Server 2005 in the same machine of a SQL server 2000. No big problems, but from the 2000 em I can't reach the 2005 Server... it says: SQL-DMO error ... apart of this, I can open both em and both databases seem to work and run.Ports. I changed the TCP/IP port of the 2005 instance to an arbitrary 1443 (the other is in the usual 1433).I configured my ODBC driver to go to that new port... but it always gives me a "login error"... and I checked tons of times the username/password so I'm sure it's correct.Some options: - OK, the driver doesn't work with 2005 - This configuration with 2 SQL Servers in the same machine, and one 2000 and other 2005 is not very good, so probably the driver would work if I just install a 2005 alone in one machine. - .... ?Any sggestions?Thank you,  RegardsFran |
|
|
AjarnMark
SQL Slashing Gunting Master
3246 Posts |
Posted - 2005-10-10 : 17:41:07
|
| I would not expect the SQL 2000 Enterprise Manager to be able to work with SQL 2005. However, the reverse is likely, that SQL 2005 Management Studio should connect okay to SQL 2000.Are you able to successfully login to SQL 2005 with the same user and password in some way other than through the ODBC driver? Or have you only been able to successfully open the SQL 2005 through some other account, such as an admin Windows account?I'm assuming that since you mentioned checking the password, that you are using a SQL Server Login, and not a trusted Windows account. Did you create the login specifically in the SQL 2005 instance? Or were you assuming that the one from 2000 would be good on both?---------------------------EmeraldCityDomains.com |
 |
|
|
penumatsa
Constraint Violating Yak Guru
289 Posts |
Posted - 2005-10-11 : 01:15:46
|
| The SQL Server 2000 EM wont work with the SQL Server 2005. But you can use the SQL 2005 Management studio to connect to SQL 2000. I dont think installing both the versions will be pose a problem. I have been running both of them on the same machine and havent encountered any problems so far.By the way, which CTP of SQL 2005 are you using?suresh penumatsa |
|
|
|
Hipogrito
Starting Member
4 Posts |
Posted - 2005-10-11 : 11:24:48
|
| Hello:Thanks for the answers!First... ok, now I know that from SQL Server em 2000 I shouldn't expect to reach 2005. In the opposite way it works ok. Thanks.Now to the Thing...I was told today that the ODBC should work... so now I have to play the right key in my SQL Server 2005 installation SQL Server 2005 September CTPI use SQL Server login in both systems (2000 and 2005)... user2000/password2000 and user2005/password2005. Independent users, each one created in their corresponding em (In fact I'm using sa user just for this test). In the ODBC I have to put this login/password to make the proper connection.I write the same kind of things in the ODBC files and I can enter in the 2000 and not in the 2005. This is what produces me more confusion... all the parameters are similar in both cases.By the way the instances are named:SQL2000: MYMACHINESQL2005: MYMACHINE\ANOTHERINSTANCENAMEAnd I just make the tcp/ip change of port to set each instance in different ports. My ODBC doesn't know about instance names but about port numbers and hosts.I didn't try to reach the SQL2005 from other place apart than from SQL2000 (It is not possible) and from the ODBC.... maybe I should try to reach this db from other place as you told me.I have to be missing something here... Anyway, thank you, and I let you know the solution if I find it.Best regardsFran |
|
|
|
aakash
Starting Member
8 Posts |
Posted - 2005-10-19 : 20:31:20
|
| As others mentioned:1. Can you connect to your SQL2005 server (at port 1443) using management studio?2. Have you checked to see that tcp connections to SQL2005 are enabled? By default, SQL2005 ships with only shared memory enabled (in the interests of security). You can check this in the SQL Server 2005 Surface configuration manager.-AakashDeveloper, SQL Server engine |
|
|
|
drobinson
Starting Member
1 Post |
Posted - 2005-11-17 : 08:49:57
|
| The solution i found was after I enabled the TCP/IP protocol, some versions forget to tell you that you must restart the service after you enable that protocol. I restarted the SQL Server and the agent and the browser....not sure which one allowed it, but it works now ....yeh |
|
|
|
derrickleggett
Pointy Haired Yak DBA
4184 Posts |
Posted - 2005-11-17 : 20:38:54
|
| You also should really upgrade to the RTM product if you can. It seems to be much more stable and run faster than the Sept CTP.MeanOldDBAderrickleggett@hotmail.comWhen life gives you a lemon, fire the DBA. |
|
|
|
|
|
|
|
|
Another topic about SQLS 2000 and 2005 together