November 30, 2010 at 10:57 am
I am trying to install SQL 2005 Standrad on a Win 2008 machine and during the installation i got some warning messages"
known compatibility issue with this version og windows
"for SQL Server and Visual Studio but i ignored and continued. Does this give me any issues while using visual studio or SQL server ?
November 30, 2010 at 10:59 am
Update before you run and you should be fine.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
November 30, 2010 at 11:20 am
what do you mean by "update before runnig" , do i have to update OS to 2003 from 2008? I would like to install SQL 2005 on Win 2008 machine, I do not have other option.
November 30, 2010 at 12:40 pm
Microsoft Update service. Make sure you have all the service packs for the OS and for SQL. www.update.microsoft.com
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
November 30, 2010 at 12:45 pm
Apply service pack 3 for SQL and it'll be fine.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 30, 2010 at 1:15 pm
yes, i applied SP3 and even during SP3 installation it gave me a warning message about compatability, do you guys think that is fine. thanks
November 30, 2010 at 1:19 pm
It works fine with service pack 3. I have more than one SQL 2005 instance on Server 2008 R2
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 30, 2010 at 1:27 pm
The warning is because SQL Server 2005 does not recognize W2K8. That OS was not around when SSK5 was released. So it warns you about potential issues.
Getting to SP3 will ensure that everything works fine.
There are a few notes on this:
http://www.microsoft.com/windowsserver2008/en/us/supported-applications.aspx
December 7, 2010 at 11:55 am
another thing i found that though we have same version of sql 2005 but diffferent OS, we can not connect to database engine residing on 2003 OS from 2008 OS,am i right? or is there a work around ?
December 7, 2010 at 12:16 pm
I don't think that is correct.
What is the error message that you are getting ?
Thank You,
Best Regards,
SQLBuddy
December 7, 2010 at 1:41 pm
Tara-1044200 (12/7/2010)
another thing i found that though we have same version of sql 2005 but diffferent OS, we can not connect to database engine residing on 2003 OS from 2008 OS,am i right?
No. I often do that, works fine. Something else must be wrong, check the error logs.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
December 7, 2010 at 2:10 pm
I get this error.
TITLE: Connect to Server
------------------------------
Cannot connect to OBBEAVER-D1 .
------------------------------
ADDITIONAL INFORMATION:
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 5)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=5&LinkId=20476
------------------------------
BUTTONS:
OK
------------------------------
December 7, 2010 at 2:12 pm
Is the server configured to allow remote connections?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
December 7, 2010 at 2:15 pm
yes, its allowed.
December 7, 2010 at 3:05 pm
This could most probably due to
1. SQL Server service is stoped on the server you are trying to connect or
2. It is using Dedicated (Static) ports
Could you check these 2 things.
Thank You,
Best Regards,
SQLBuddy
Viewing 15 posts - 1 through 15 (of 21 total)
You must be logged in to reply to this topic. Login to reply