First is can I use Windows XP with the client tools (Enterprise Manager) to
connect to MS SQL Server 2000? If so, can someone explaine? I have tried
using SQL Server Authentication but I get an error saying server does not
exit or access denied. I tried using the SA account and that does not work
either.
Thanks,Yes you should be able to . One gotcha is that XP Home always
authenticates as Guest.
Create a Test ODBC DSN to get a better error message if you can't connect.
Check the OS error number.
Example:
OS Error 10061 = Connection Refused. Server is not listening on the socket.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
Showing posts with label tools. Show all posts
Showing posts with label tools. Show all posts
Thursday, March 22, 2012
Can not connect to MS SQL server 2000 with Windows XP
First is can I use Windows XP with the client tools (Enterprise Manager) to
connect to MS SQL Server 2000? If so, can someone explaine? I have tried
using SQL Server Authentication but I get an error saying server does not
exit or access denied. I tried using the SA account and that does not work
either.
Thanks,
Yes you should be able to . One gotcha is that XP Home always
authenticates as Guest.
Create a Test ODBC DSN to get a better error message if you can't connect.
Check the OS error number.
Example:
OS Error 10061 = Connection Refused. Server is not listening on the socket.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
connect to MS SQL Server 2000? If so, can someone explaine? I have tried
using SQL Server Authentication but I get an error saying server does not
exit or access denied. I tried using the SA account and that does not work
either.
Thanks,
Yes you should be able to . One gotcha is that XP Home always
authenticates as Guest.
Create a Test ODBC DSN to get a better error message if you can't connect.
Check the OS error number.
Example:
OS Error 10061 = Connection Refused. Server is not listening on the socket.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
Wednesday, March 7, 2012
Can I Use SQL Server 2005 Developer Edition For Client Tools?
My ISP has me licensed for a production SQL Server 2005 database, yet they
cannot provide me with the client tools that I need, specifically SQL Server
Management Studio and SQL Server Business Intelligence Development Studio.
If I purchase SQL Server 2005 Developer Edition will it have these two tools,
and will I be able to work with my production SQL database? Just for
clarification, I use the Business Intelligence studio to drop my existing
tables, and I migrate from locally-stored ACCESS databases to my production
SQL Server 2005 each night.On Jul 30, 3:46 pm, MIA Mark <MIAM...@.discussions.microsoft.com>
wrote:
> My ISP has me licensed for a production SQL Server 2005 database, yet they
> cannot provide me with the client tools that I need, specifically SQL Server
> Management Studio and SQL Server Business Intelligence Development Studio.
> If I purchase SQL Server 2005 Developer Edition will it have these two tools,
> and will I be able to work with my production SQL database? Just for
> clarification, I use the Business Intelligence studio to drop my existing
> tables, and I migrate from locally-stored ACCESS databases to my production
> SQL Server 2005 each night.
Yes, this should be fine. The licensing might be a bit of a gray area
though; but, I think that the ISP license should cover the production
deployment.
http://www.microsoft.com/sql/prodinfo/features/compare-features.mspx
Regards,
Enrique Martinez
Sr. Software Consultant
cannot provide me with the client tools that I need, specifically SQL Server
Management Studio and SQL Server Business Intelligence Development Studio.
If I purchase SQL Server 2005 Developer Edition will it have these two tools,
and will I be able to work with my production SQL database? Just for
clarification, I use the Business Intelligence studio to drop my existing
tables, and I migrate from locally-stored ACCESS databases to my production
SQL Server 2005 each night.On Jul 30, 3:46 pm, MIA Mark <MIAM...@.discussions.microsoft.com>
wrote:
> My ISP has me licensed for a production SQL Server 2005 database, yet they
> cannot provide me with the client tools that I need, specifically SQL Server
> Management Studio and SQL Server Business Intelligence Development Studio.
> If I purchase SQL Server 2005 Developer Edition will it have these two tools,
> and will I be able to work with my production SQL database? Just for
> clarification, I use the Business Intelligence studio to drop my existing
> tables, and I migrate from locally-stored ACCESS databases to my production
> SQL Server 2005 each night.
Yes, this should be fine. The licensing might be a bit of a gray area
though; but, I think that the ISP license should cover the production
deployment.
http://www.microsoft.com/sql/prodinfo/features/compare-features.mspx
Regards,
Enrique Martinez
Sr. Software Consultant
Friday, February 10, 2012
Can I install the SQL Server 2005 client tools in NT4 Server with Service Pack 6?
Can I install the SQL Server 2005 client tools in NT4 Server with Service Pack 6?
I tried, and I get an error indicating that "the specified program requires a newer version of windows". DOes that mean I need to upgrade to W2K or W2K3? Some of our (legacy) components only work in NT4 but must now get data from SQL 2005 instead of SQL 2000, and I can't get the drivers installed in NT.
Any ideas, workarounds, etc.? Anything will help...
As you have the MDAC package installed on the WIndows NT Server you shoul dhave access to SQL Server. SQL Server does not need the SQL Native Client if you don′t use any sphisticated new feature of SQL Server 2k5 that the client needs access within his client library. For just plain data access it should be enough to have MDAC installed.HTH, jens Suessmeyer.
http://www.sqlserver2005.de
Subscribe to:
Posts (Atom)