Can Sql 2000 and 2005 express work together?

I have a server (win server 2003) that is running Symantec Backup Exec for backups. I found that this soft uses an SQL server 2000 instance to keep his data... The problem is that I developed an application in asp.net (with VS2003) that use an SQL server 2005 express database. What I want to know is if I install SQL server 2005 express, is the backup will still work? I mean that the 2005 express wont upgrade sql 2000? What do I have to do to make it works?

hi,

SQL Server 2000 (including MSDE) and SQL Server 2005 (including SQLExpress) cna be installed "side by side"...

you can install up to 16 different instances per box, and each instance will maintain it's own binaries and registry settings separated from all other instances.. even at different service pack levels..

obviously you have not to mismatch instance's names.. only 1 instance per box can be the "default" instance, known as "ComputerName" or "." or "(Local)" (the last 2 only for local connections), where all the other instances have to be "named" instances, known as "ComputerName\InstanceName" or ".\InstanceName" or "(Local)\InstanceName" ... further info at http://msdn2.microsoft.com/en-us/library/ms143547.aspx

a little "note" should be mentioned about shared components.. this binaries are actually shared among all instances of the same code base.. so all 2000 related shared binaries will be shared among all 2000 instances, where 2005 shared components will be shared with all 2005 instances, at the higher service pack level..

another "side note".. and this is COM related.. COM components do not allow "side by side" implementation, so that SQL Server 2005 installs some of them at the 2005 edition level.. and SQL Server 2000 will "inherit" those components.. think about SQL-DMO and the like, but you should not be interested with that as 2005 versions are downwards compatible...

regards

|||Thanks a lot!

can not remote connect SQL 2000

Hello,
We have 3 SQL servers.
Server01 Win 2003 w/SQL 2000 192.168.1.1
Server02 Win 2003 w/SQL 2000 192.168.1.2
Server03 Win 2003 w/SQL 2005 192.168.1.3
Server02 can see Server01 and Server03.
Server01 and Server03 can find each other but can not see Server02.
I add 192.168.1.2 in Server03 SQL native client configuration.
The server03 error message said 'the SQL does not allow remote connection'
Whe I check Server02 SQL property, the remote connection is checked.
How can I fix this problem?
Thanks
It's more than just visibility. As I discuss in Chapter 9, you'll need to
enable the protocols and (in the case of SQL Server 2005) the SQL Browser
service to expose SQL Server to the network.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"Newbie" <Newbie@.discussions.microsoft.com> wrote in message
news:1F8BFB61-5920-4087-B020-273471DA6163@.microsoft.com...
> Hello,
> We have 3 SQL servers.
> Server01 Win 2003 w/SQL 2000 192.168.1.1
> Server02 Win 2003 w/SQL 2000 192.168.1.2
> Server03 Win 2003 w/SQL 2005 192.168.1.3
> Server02 can see Server01 and Server03.
> Server01 and Server03 can find each other but can not see Server02.
> I add 192.168.1.2 in Server03 SQL native client configuration.
> The server03 error message said 'the SQL does not allow remote connection'
> Whe I check Server02 SQL property, the remote connection is checked.
> How can I fix this problem?
> Thanks
|||Hello,
My question is both SQL2000 can see SQL2005, but SQL2005 can not connect one
of SQL2000.
Thanks
"William (Bill) Vaughn" wrote:

> It's more than just visibility. As I discuss in Chapter 9, you'll need to
> enable the protocols and (in the case of SQL Server 2005) the SQL Browser
> service to expose SQL Server to the network.
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no rights.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ------
> "Newbie" <Newbie@.discussions.microsoft.com> wrote in message
> news:1F8BFB61-5920-4087-B020-273471DA6163@.microsoft.com...
>
>

can not remote connect SQL 2000

Hello,
We have 3 SQL servers.
Server01 Win 2003 w/SQL 2000 192.168.1.1
Server02 Win 2003 w/SQL 2000 192.168.1.2
Server03 Win 2003 w/SQL 2005 192.168.1.3
Server02 can see Server01 and Server03.
Server01 and Server03 can find each other but can not see Server02.
I add 192.168.1.2 in Server03 SQL native client configuration.
The server03 error message said 'the SQL does not allow remote connection'
Whe I check Server02 SQL property, the remote connection is checked.
How can I fix this problem?
ThanksIt's more than just visibility. As I discuss in Chapter 9, you'll need to
enable the protocols and (in the case of SQL Server 2005) the SQL Browser
service to expose SQL Server to the network.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
"Newbie" <Newbie@.discussions.microsoft.com> wrote in message
news:1F8BFB61-5920-4087-B020-273471DA6163@.microsoft.com...
> Hello,
> We have 3 SQL servers.
> Server01 Win 2003 w/SQL 2000 192.168.1.1
> Server02 Win 2003 w/SQL 2000 192.168.1.2
> Server03 Win 2003 w/SQL 2005 192.168.1.3
> Server02 can see Server01 and Server03.
> Server01 and Server03 can find each other but can not see Server02.
> I add 192.168.1.2 in Server03 SQL native client configuration.
> The server03 error message said 'the SQL does not allow remote connection'
> Whe I check Server02 SQL property, the remote connection is checked.
> How can I fix this problem?
> Thanks|||Hello,
My question is both SQL2000 can see SQL2005, but SQL2005 can not connect one
of SQL2000.
Thanks
"William (Bill) Vaughn" wrote:

> It's more than just visibility. As I discuss in Chapter 9, you'll need to
> enable the protocols and (in the case of SQL Server 2005) the SQL Browser
> service to expose SQL Server to the network.
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ----
---
> "Newbie" <Newbie@.discussions.microsoft.com> wrote in message
> news:1F8BFB61-5920-4087-B020-273471DA6163@.microsoft.com...
>
>

can not login sql server

Hello,
We have a Win 2003 server with SQL 2000 installed. When we upgrade Win 2003
server to Active Directory, then the SQL 2000 can not work any more.
We try to uninstall and install again, window mode or mixed mode.
The error message alwsays say "xxx/administrator is not associated with
trusted SQL server connection" or "login failed for user sa"
ThanksSo you promoted the Server to a domain controller ? The local Administrator
is deactivated with promoting the Server. Although the domain administrators
group is still working and should be associated with the
SystemAdministrators group. I wonder what security Account you typed in for
starting the sql Service ? Did you put in the system account or the
Administrators account ? If you put in the local admin account change it to
start up the server. When do you get thios messages ?
HTH, Jens Smeyer.
"Newbie" <Newbie@.discussions.microsoft.com> schrieb im Newsbeitrag
news:1FA3AC6A-C62A-4570-8242-BE4EBA273DA1@.microsoft.com...
> Hello,
> We have a Win 2003 server with SQL 2000 installed. When we upgrade Win
> 2003
> server to Active Directory, then the SQL 2000 can not work any more.
> We try to uninstall and install again, window mode or mixed mode.
> The error message alwsays say "xxx/administrator is not associated with
> trusted SQL server connection" or "login failed for user sa"
> Thanks|||So you promoted the Server to a domain controller ?
Yes.
The local Administrator is deactivated with promoting the Server. Although
the domain administrators group is still working and should be associated
with the SystemAdministrators group.
I wonder what security Account you typed in for starting the sql Service ?
Did you put in the system account or the Administrators account ?
If you put in the local admin account change it to start up the server. When
do you get this messages ?
I tried administrator first, the error message is "xxx/administrator is not
associated with trusted SQL server connection"
Then I installed again with mixed mode, the error message is "login failed
for user sa"
Thanks

can not login sql server

Hello,
We have a Win 2003 server with SQL 2000 installed. When we upgrade Win 2003
server to Active Directory, then the SQL 2000 can not work any more.
We try to uninstall and install again, window mode or mixed mode.
The error message alwsays say "xxx/administrator is not associated with
trusted SQL server connection" or "login failed for user sa"
ThanksSo you promoted the Server to a domain controller ? The local Administrator
is deactivated with promoting the Server. Although the domain administrators
group is still working and should be associated with the
SystemAdministrators group. I wonder what security Account you typed in for
starting the sql Service ? Did you put in the system account or the
Administrators account ? If you put in the local admin account change it to
start up the server. When do you get thios messages ?
HTH, Jens Süßmeyer.
"Newbie" <Newbie@.discussions.microsoft.com> schrieb im Newsbeitrag
news:1FA3AC6A-C62A-4570-8242-BE4EBA273DA1@.microsoft.com...
> Hello,
> We have a Win 2003 server with SQL 2000 installed. When we upgrade Win
> 2003
> server to Active Directory, then the SQL 2000 can not work any more.
> We try to uninstall and install again, window mode or mixed mode.
> The error message alwsays say "xxx/administrator is not associated with
> trusted SQL server connection" or "login failed for user sa"
> Thanks|||So you promoted the Server to a domain controller ?
Yes.
The local Administrator is deactivated with promoting the Server. Although
the domain administrators group is still working and should be associated
with the SystemAdministrators group.
I wonder what security Account you typed in for starting the sql Service ?
Did you put in the system account or the Administrators account ?
If you put in the local admin account change it to start up the server. When
do you get this messages ?
I tried administrator first, the error message is "xxx/administrator is not
associated with trusted SQL server connection"
Then I installed again with mixed mode, the error message is "login failed
for user sa"
Thanks

can not login sql server

Hello,
We have a Win 2003 server with SQL 2000 installed. When we upgrade Win 2003
server to Active Directory, then the SQL 2000 can not work any more.
We try to uninstall and install again, window mode or mixed mode.
The error message alwsays say "xxx/administrator is not associated with
trusted SQL server connection" or "login failed for user sa"
Thanks
So you promoted the Server to a domain controller ? The local Administrator
is deactivated with promoting the Server. Although the domain administrators
group is still working and should be associated with the
SystemAdministrators group. I wonder what security Account you typed in for
starting the sql Service ? Did you put in the system account or the
Administrators account ? If you put in the local admin account change it to
start up the server. When do you get thios messages ?
HTH, Jens Smeyer.
"Newbie" <Newbie@.discussions.microsoft.com> schrieb im Newsbeitrag
news:1FA3AC6A-C62A-4570-8242-BE4EBA273DA1@.microsoft.com...
> Hello,
> We have a Win 2003 server with SQL 2000 installed. When we upgrade Win
> 2003
> server to Active Directory, then the SQL 2000 can not work any more.
> We try to uninstall and install again, window mode or mixed mode.
> The error message alwsays say "xxx/administrator is not associated with
> trusted SQL server connection" or "login failed for user sa"
> Thanks
|||So you promoted the Server to a domain controller ?
Yes.
The local Administrator is deactivated with promoting the Server. Although
the domain administrators group is still working and should be associated
with the SystemAdministrators group.
I wonder what security Account you typed in for starting the sql Service ?
Did you put in the system account or the Administrators account ?
If you put in the local admin account change it to start up the server. When
do you get this messages ?
I tried administrator first, the error message is "xxx/administrator is not
associated with trusted SQL server connection"
Then I installed again with mixed mode, the error message is "login failed
for user sa"
Thanks

can not load xpstar.dll

hi,
i have sql server sp3 running upon win 2000 adv server sp 4. the server is
configured for merge replication with another machine with same
configuration (sql server sp3 running upon win 2000 adv server sp 4). few
days back i recieved this error when i was trying to connect SQL server
remotely from one macine to the other.
Microsoft SQL-DMO(ODMC SQL State:42000) Error 0: cannot load the dll
xpstar.dll, or one of the DLLs it refferences. Reason: 126(the specified
module could not be found)
even if i could connect, i get the same error upon almost every activity on
the remote sql server. i found no reasonable solution to the problem on the
internet. finnally i uninsalled the sql server and then installed fresh sql
server and sp3. the problem was resolved. but afetr few days, i m facing
the same problem back again. i have repeated the same course of action.
i need to know any why this is happning so i could reach to the root of the
problem. installing back the sql server is not an optimal solution. need
help and fast.
thanx in advance.
Atif Chowhan
When you check you will find that xpstar.dll is actually there and loaded. The file missing is probably shfolder.dll. This folder resides in %systemRoot%\system32, copy it from any other server.
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine supports Post Alerts, Ratings, and Searching.

can not load xpstar.dll

hi,
i have sql server sp3 running upon win 2000 adv server sp 4. the server is
configured for merge replication with another machine with same
configuration (sql server sp3 running upon win 2000 adv server sp 4). few
days back i recieved this error when i was trying to connect SQL server
remotely from one macine to the other.
Microsoft SQL-DMO(ODMC SQL State:42000) Error 0: cannot load the dll
xpstar.dll, or one of the DLLs it refferences. Reason: 126(the specified
module could not be found)
even if i could connect, i get the same error upon almost every activity on
the remote sql server. i found no reasonable solution to the problem on the
internet. finnally i uninsalled the sql server and then installed fresh sql
server and sp3. the problem was resolved. but afetr few days, i m facing
the same problem back again. i have repeated the same course of action.
i need to know any why this is happning so i could reach to the root of the
problem. installing back the sql server is not an optimal solution. need
help and fast.
thanx in advance.
Atif ChowhanWhen you check you will find that xpstar.dll is actually there and loaded. The file missing is probably shfolder.dll. This folder resides in %systemRoot%\system32, copy it from any other server.
--
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine supports Post Alerts, Ratings, and Searching.