Hi!
Im having the fallowing error when I try to open/access a linked server
Error:
Error 7302: Could not create an instance of OLE DB provider 'MSOLAP.2'.
OLE DB error trace [Non-interface error: CoCreate of DSO for MSOLAP.2 returned 0x80004005].
I have already tried to create the server using SEM and also with SQL syntax in ISQLW.
Code:
EXEC sp_addlinkedserver
@.server='LINKED_OLAP',
@.srvproduct='',
@.provider='MSOLAP.2',
@.datasrc='MyServerName.MyDomain,
@.catalog='MyDataBase'
Im allowed to create the linked server but I cant use it.
Information:
OS: Windows 2003EE
SQL: MSSQL 2000 + SP3a
MDAC: MDAC2.8 rtm
Thanks,
Paulowhen referring to objects defined in a linked server, you should use the convention:
servername.databasename.userid.object|||That it's not the problem for sure.|||I'd see if any of Microsoft's (http://search.microsoft.com/search/results.aspx?view=msdn&st=b&na=82&qu=0x80004005+OLAP&s=1) ideas help.
-PatP|||Thanks, but none of the links apply to.
Paulo
Showing posts with label instance. Show all posts
Showing posts with label instance. Show all posts
Monday, March 26, 2012
Wednesday, March 21, 2012
Error on MSDTC after a SQL Server fail-over
Hello
I have a SQL Server 2000 64 bits running on an two node cluster (NODE1 and
NODE2) with two SQL Server instances (SQL1 and SQL1\2).
Instance SQL1 is running on NODE1 and instance SQL1\2 is running on NODE2.
MSDTC is configured on a exclusive group and it is running on NODE1.
The Cluster Group also is running on NODE1.
I use a lot of distributed transactions between SQL1\2 and SQL1 and it works
just fine.
I had a problem last night with NODE1, and all the resources (Cluster, SQL1
and MSDTC) failed to NODE2.
After the failover I started getting the error below when trying to execute
a distributed transaction from SQL1\2 to SQL1.
Error: 8510, Severity: 20, State: 2
Enlist of MSDTC transaction failed: XACT_E_CONNECTION_DOWN.
The error happened during the failover and also after the finish of the
failver.
On SQL1 error log I notice that there was no error messages when it
initialize the MSDTC. Below is the message from the ErrorLog.
"Attempting to initialize Distributed Transaction Coordinator."
To solve the Error I brought up NODE1 back on-line (it failed because of a
network problem). I move the MSDTC back to NODE1, move SQL1 back to NODE1 and
also re-started SQL1\2 on NODE2 (brought offline, bring on-line). After that
procedure I was able to use distributed transactions between SQL1 and SQL1\2.
I would like to know why that problem happened?
I suposed that MSDTC was able to work on cluster and that the MSDTC should
work after a failover.
I would like your help to understand the problem. If you need more
information just let me know.
Regards.
Carlos Eduardo Selonke de Souza
http://carlos.geekbunker.org
Hi Carlos
MSDTC has to be running when SQL is starting. So it's a timing problem. To
be certain, check the log in SQL, and look for messages about finding the
Transaction "Server". It probably states that is was down. SQL will not retry
it afterwards.
If the MSDTC resource was in the same group as the SQL Virtual Server, you
could make SQL dependant of MSDTC, but unfortunately this is not the case.
Chau chau,
Pascalos
"Carlos Selonke" wrote:
> Hello
> I have a SQL Server 2000 64 bits running on an two node cluster (NODE1 and
> NODE2) with two SQL Server instances (SQL1 and SQL1\2).
> Instance SQL1 is running on NODE1 and instance SQL1\2 is running on NODE2.
> MSDTC is configured on a exclusive group and it is running on NODE1.
> The Cluster Group also is running on NODE1.
> I use a lot of distributed transactions between SQL1\2 and SQL1 and it works
> just fine.
> I had a problem last night with NODE1, and all the resources (Cluster, SQL1
> and MSDTC) failed to NODE2.
> After the failover I started getting the error below when trying to execute
> a distributed transaction from SQL1\2 to SQL1.
> Error: 8510, Severity: 20, State: 2
> Enlist of MSDTC transaction failed: XACT_E_CONNECTION_DOWN.
> The error happened during the failover and also after the finish of the
> failver.
> On SQL1 error log I notice that there was no error messages when it
> initialize the MSDTC. Below is the message from the ErrorLog.
> "Attempting to initialize Distributed Transaction Coordinator."
> To solve the Error I brought up NODE1 back on-line (it failed because of a
> network problem). I move the MSDTC back to NODE1, move SQL1 back to NODE1 and
> also re-started SQL1\2 on NODE2 (brought offline, bring on-line). After that
> procedure I was able to use distributed transactions between SQL1 and SQL1\2.
> I would like to know why that problem happened?
> I suposed that MSDTC was able to work on cluster and that the MSDTC should
> work after a failover.
> I would like your help to understand the problem. If you need more
> information just let me know.
> Regards.
> --
> Carlos Eduardo Selonke de Souza
> http://carlos.geekbunker.org
I have a SQL Server 2000 64 bits running on an two node cluster (NODE1 and
NODE2) with two SQL Server instances (SQL1 and SQL1\2).
Instance SQL1 is running on NODE1 and instance SQL1\2 is running on NODE2.
MSDTC is configured on a exclusive group and it is running on NODE1.
The Cluster Group also is running on NODE1.
I use a lot of distributed transactions between SQL1\2 and SQL1 and it works
just fine.
I had a problem last night with NODE1, and all the resources (Cluster, SQL1
and MSDTC) failed to NODE2.
After the failover I started getting the error below when trying to execute
a distributed transaction from SQL1\2 to SQL1.
Error: 8510, Severity: 20, State: 2
Enlist of MSDTC transaction failed: XACT_E_CONNECTION_DOWN.
The error happened during the failover and also after the finish of the
failver.
On SQL1 error log I notice that there was no error messages when it
initialize the MSDTC. Below is the message from the ErrorLog.
"Attempting to initialize Distributed Transaction Coordinator."
To solve the Error I brought up NODE1 back on-line (it failed because of a
network problem). I move the MSDTC back to NODE1, move SQL1 back to NODE1 and
also re-started SQL1\2 on NODE2 (brought offline, bring on-line). After that
procedure I was able to use distributed transactions between SQL1 and SQL1\2.
I would like to know why that problem happened?
I suposed that MSDTC was able to work on cluster and that the MSDTC should
work after a failover.
I would like your help to understand the problem. If you need more
information just let me know.
Regards.
Carlos Eduardo Selonke de Souza
http://carlos.geekbunker.org
Hi Carlos
MSDTC has to be running when SQL is starting. So it's a timing problem. To
be certain, check the log in SQL, and look for messages about finding the
Transaction "Server". It probably states that is was down. SQL will not retry
it afterwards.
If the MSDTC resource was in the same group as the SQL Virtual Server, you
could make SQL dependant of MSDTC, but unfortunately this is not the case.
Chau chau,
Pascalos
"Carlos Selonke" wrote:
> Hello
> I have a SQL Server 2000 64 bits running on an two node cluster (NODE1 and
> NODE2) with two SQL Server instances (SQL1 and SQL1\2).
> Instance SQL1 is running on NODE1 and instance SQL1\2 is running on NODE2.
> MSDTC is configured on a exclusive group and it is running on NODE1.
> The Cluster Group also is running on NODE1.
> I use a lot of distributed transactions between SQL1\2 and SQL1 and it works
> just fine.
> I had a problem last night with NODE1, and all the resources (Cluster, SQL1
> and MSDTC) failed to NODE2.
> After the failover I started getting the error below when trying to execute
> a distributed transaction from SQL1\2 to SQL1.
> Error: 8510, Severity: 20, State: 2
> Enlist of MSDTC transaction failed: XACT_E_CONNECTION_DOWN.
> The error happened during the failover and also after the finish of the
> failver.
> On SQL1 error log I notice that there was no error messages when it
> initialize the MSDTC. Below is the message from the ErrorLog.
> "Attempting to initialize Distributed Transaction Coordinator."
> To solve the Error I brought up NODE1 back on-line (it failed because of a
> network problem). I move the MSDTC back to NODE1, move SQL1 back to NODE1 and
> also re-started SQL1\2 on NODE2 (brought offline, bring on-line). After that
> procedure I was able to use distributed transactions between SQL1 and SQL1\2.
> I would like to know why that problem happened?
> I suposed that MSDTC was able to work on cluster and that the MSDTC should
> work after a failover.
> I would like your help to understand the problem. If you need more
> information just let me know.
> Regards.
> --
> Carlos Eduardo Selonke de Souza
> http://carlos.geekbunker.org
Error on install
I'm trying to install an instance of Reporting Services onto a 2003 Server.
Everything works great until I get to the part where I connect it to a
database. I'm attempting to connect it to a SQL 2005 server. I get an error
when it trys to "Create A Grants Rights Script." Here's the rest of the error:
System.Management.ManagementException: Access denied
at
System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus
errorCode)
at System.Management.ManagementScope.InitializeGuts(Object o)
at System.Management.ManagementScope.Initialize()
at System.Management.ManagementObjectSearcher.Initialize()
at System.Management.ManagementObjectSearcher.Get()
at Microsoft.ReportingServices.Diagnostics.WebUtil.GetIPAddresses(String
machine)
at
ReportServicesConfigUI.Panels.DatabaseSetupPanel.IsLocalDbServer(String
dbServer)
at
ReportServicesConfigUI.Panels.DatabaseSetupPanel.SetDatabaseConnectionTask(String
connectionString, String server, String database,
ConfigurationCredentialsType credsType, String account, String password,
Boolean upgrade, String dbVersion)
Now. There should be no reson for me to get an access denied error on this
portion. I've tried it 2 different ways. First, I've tried using my windows
credentials. I'm the system dba with all the access, secondly, I've tried
creating a sql account will all the access I can possibly give it, and I
still get this error.
Any ideas anyone has would be great.
-- CaseyHi Casey,
I am having same problem, do you have any luck?
thanks.
SKip
"Casey" wrote:
> I'm trying to install an instance of Reporting Services onto a 2003 Server.
> Everything works great until I get to the part where I connect it to a
> database. I'm attempting to connect it to a SQL 2005 server. I get an error
> when it trys to "Create A Grants Rights Script." Here's the rest of the error:
> System.Management.ManagementException: Access denied
> at
> System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus
> errorCode)
> at System.Management.ManagementScope.InitializeGuts(Object o)
> at System.Management.ManagementScope.Initialize()
> at System.Management.ManagementObjectSearcher.Initialize()
> at System.Management.ManagementObjectSearcher.Get()
> at Microsoft.ReportingServices.Diagnostics.WebUtil.GetIPAddresses(String
> machine)
> at
> ReportServicesConfigUI.Panels.DatabaseSetupPanel.IsLocalDbServer(String
> dbServer)
> at
> ReportServicesConfigUI.Panels.DatabaseSetupPanel.SetDatabaseConnectionTask(String
> connectionString, String server, String database,
> ConfigurationCredentialsType credsType, String account, String password,
> Boolean upgrade, String dbVersion)
> Now. There should be no reson for me to get an access denied error on this
> portion. I've tried it 2 different ways. First, I've tried using my windows
> credentials. I'm the system dba with all the access, secondly, I've tried
> creating a sql account will all the access I can possibly give it, and I
> still get this error.
> Any ideas anyone has would be great.
> -- Casey|||Hi,
I am also having the same problem. Please anybody has an answer the this?
Thanks,
Henry
"Skip" wrote:
> Hi Casey,
> I am having same problem, do you have any luck?
> thanks.
> SKip
> "Casey" wrote:
> > I'm trying to install an instance of Reporting Services onto a 2003 Server.
> > Everything works great until I get to the part where I connect it to a
> > database. I'm attempting to connect it to a SQL 2005 server. I get an error
> > when it trys to "Create A Grants Rights Script." Here's the rest of the error:
> >
> > System.Management.ManagementException: Access denied
> > at
> > System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus
> > errorCode)
> > at System.Management.ManagementScope.InitializeGuts(Object o)
> > at System.Management.ManagementScope.Initialize()
> > at System.Management.ManagementObjectSearcher.Initialize()
> > at System.Management.ManagementObjectSearcher.Get()
> > at Microsoft.ReportingServices.Diagnostics.WebUtil.GetIPAddresses(String
> > machine)
> > at
> > ReportServicesConfigUI.Panels.DatabaseSetupPanel.IsLocalDbServer(String
> > dbServer)
> > at
> > ReportServicesConfigUI.Panels.DatabaseSetupPanel.SetDatabaseConnectionTask(String
> > connectionString, String server, String database,
> > ConfigurationCredentialsType credsType, String account, String password,
> > Boolean upgrade, String dbVersion)
> >
> > Now. There should be no reson for me to get an access denied error on this
> > portion. I've tried it 2 different ways. First, I've tried using my windows
> > credentials. I'm the system dba with all the access, secondly, I've tried
> > creating a sql account will all the access I can possibly give it, and I
> > still get this error.
> >
> > Any ideas anyone has would be great.
> >
> > -- Casey
Everything works great until I get to the part where I connect it to a
database. I'm attempting to connect it to a SQL 2005 server. I get an error
when it trys to "Create A Grants Rights Script." Here's the rest of the error:
System.Management.ManagementException: Access denied
at
System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus
errorCode)
at System.Management.ManagementScope.InitializeGuts(Object o)
at System.Management.ManagementScope.Initialize()
at System.Management.ManagementObjectSearcher.Initialize()
at System.Management.ManagementObjectSearcher.Get()
at Microsoft.ReportingServices.Diagnostics.WebUtil.GetIPAddresses(String
machine)
at
ReportServicesConfigUI.Panels.DatabaseSetupPanel.IsLocalDbServer(String
dbServer)
at
ReportServicesConfigUI.Panels.DatabaseSetupPanel.SetDatabaseConnectionTask(String
connectionString, String server, String database,
ConfigurationCredentialsType credsType, String account, String password,
Boolean upgrade, String dbVersion)
Now. There should be no reson for me to get an access denied error on this
portion. I've tried it 2 different ways. First, I've tried using my windows
credentials. I'm the system dba with all the access, secondly, I've tried
creating a sql account will all the access I can possibly give it, and I
still get this error.
Any ideas anyone has would be great.
-- CaseyHi Casey,
I am having same problem, do you have any luck?
thanks.
SKip
"Casey" wrote:
> I'm trying to install an instance of Reporting Services onto a 2003 Server.
> Everything works great until I get to the part where I connect it to a
> database. I'm attempting to connect it to a SQL 2005 server. I get an error
> when it trys to "Create A Grants Rights Script." Here's the rest of the error:
> System.Management.ManagementException: Access denied
> at
> System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus
> errorCode)
> at System.Management.ManagementScope.InitializeGuts(Object o)
> at System.Management.ManagementScope.Initialize()
> at System.Management.ManagementObjectSearcher.Initialize()
> at System.Management.ManagementObjectSearcher.Get()
> at Microsoft.ReportingServices.Diagnostics.WebUtil.GetIPAddresses(String
> machine)
> at
> ReportServicesConfigUI.Panels.DatabaseSetupPanel.IsLocalDbServer(String
> dbServer)
> at
> ReportServicesConfigUI.Panels.DatabaseSetupPanel.SetDatabaseConnectionTask(String
> connectionString, String server, String database,
> ConfigurationCredentialsType credsType, String account, String password,
> Boolean upgrade, String dbVersion)
> Now. There should be no reson for me to get an access denied error on this
> portion. I've tried it 2 different ways. First, I've tried using my windows
> credentials. I'm the system dba with all the access, secondly, I've tried
> creating a sql account will all the access I can possibly give it, and I
> still get this error.
> Any ideas anyone has would be great.
> -- Casey|||Hi,
I am also having the same problem. Please anybody has an answer the this?
Thanks,
Henry
"Skip" wrote:
> Hi Casey,
> I am having same problem, do you have any luck?
> thanks.
> SKip
> "Casey" wrote:
> > I'm trying to install an instance of Reporting Services onto a 2003 Server.
> > Everything works great until I get to the part where I connect it to a
> > database. I'm attempting to connect it to a SQL 2005 server. I get an error
> > when it trys to "Create A Grants Rights Script." Here's the rest of the error:
> >
> > System.Management.ManagementException: Access denied
> > at
> > System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus
> > errorCode)
> > at System.Management.ManagementScope.InitializeGuts(Object o)
> > at System.Management.ManagementScope.Initialize()
> > at System.Management.ManagementObjectSearcher.Initialize()
> > at System.Management.ManagementObjectSearcher.Get()
> > at Microsoft.ReportingServices.Diagnostics.WebUtil.GetIPAddresses(String
> > machine)
> > at
> > ReportServicesConfigUI.Panels.DatabaseSetupPanel.IsLocalDbServer(String
> > dbServer)
> > at
> > ReportServicesConfigUI.Panels.DatabaseSetupPanel.SetDatabaseConnectionTask(String
> > connectionString, String server, String database,
> > ConfigurationCredentialsType credsType, String account, String password,
> > Boolean upgrade, String dbVersion)
> >
> > Now. There should be no reson for me to get an access denied error on this
> > portion. I've tried it 2 different ways. First, I've tried using my windows
> > credentials. I'm the system dba with all the access, secondly, I've tried
> > creating a sql account will all the access I can possibly give it, and I
> > still get this error.
> >
> > Any ideas anyone has would be great.
> >
> > -- Casey
Monday, March 19, 2012
Error on Attaching SQL server 2005 DB
Hai
When i try to attach (using raw .mdf & .ldf) DB that was detached from another SQL Server 2005 instance. I got this error
The database 'Content' cannot be opened because it is version 611. This server supports version 603 and earlier. A downgrade path is not supported.
Could not open new database 'Content'. CREATE DATABASE is aborted. (Microsoft SQL Server, Error: 948)
How can i slove this Error?
Regards
It appears you are attempting to attach to some pre-RTM version of SQL.
You'll want to ensure that you are using the released version of SQL2005, and not a previous beta/ctp version.
Error on Attaching SQL server 2005 DB
Hai
When i try to attach (using raw .mdf & .ldf) DB that was detached from another SQL Server 2005 instance. I got this error
The database 'Content' cannot be opened because it is version 611. This server supports version 603 and earlier. A downgrade path is not supported.
Could not open new database 'Content'. CREATE DATABASE is aborted. (Microsoft SQL Server, Error: 948)
How can i slove this Error?
Regards
It appears you are attempting to attach to some pre-RTM version of SQL.
You'll want to ensure that you are using the released version of SQL2005, and not a previous beta/ctp version.
Error on Attaching Database
When attaching a database that was detached from another SQL Server instance.
I got the error message below:
Error 602: Could not find row in sysindexes for database ID 25, object ID 1,
index ID 1. Run DBCC CHECKTABLE on sysindexes.
i am using SQL Server 2000
Thanks and Regards
Was the database you attached from a SQL Server 2005 server? I get that error if I attach a 2005 database to a 2000 SQL Server.I don't know at this time thought if we are suppose to be able to attach a SQL 2005 database to a SQL 2000 server even if we keep it compatable.|||I also get this error when detaching a database from SQL Server 2005 and attaching to SQL Server 2000. Not sure what Microsoft's recommendation is or how to determine what might have changed in the schema to make it no longer compatible with SQL Server 2000.|||
I just hope somebody would help solve this prob coz i do have the same prob.
I can't attach a database from sql2005 back to sql2000 and it's giving me a lot of headache!
I got loads of work to do and this prob is eating my time.
Help!
|||You can't attach a 2005 database to 2000. The best you can do here is to export the data from the 2005 database and import into a 2000 database.|||It's not possible to take a sql2k5 database and attach it to sql2k. The meta data has changed drasticly on sql2k5. The change cannot be understood by sql2k.Your only option is to export/import to transfer data between the versions.|||You cannot attach a SQL Server 2005 database to SQL Server 2000 - even if this used to be a SQL Server 2000 database attached to SQL Server 2005 and attaching it back to SQL Server 2000. SQL Server 2005 changes some system objects which SQL Server 2000 does not have.|||If this is the case what is the reason for the compatability level. When I run sp_dbcmptlevel 'database' I get an 80, after I have made changes to the database with 2005 (80 is 2000, 90 is 2005). I was under the impression from a Microsoft person that this was something that could be done. I would like to do this incase we have major problems in Production after the upgrade to 2005. I have a lot of data in 50+ tables. import/Export would not be a good solution. Anyone from Microsoft care to chime in.|||Database compatibility has little to do with the changes in meta data. dbcmptlevel is set to allow sql2k5 to run the database at the current or lower settings.
This issue is very much not isolated. It's the same if you take a Mpeg4 file and try to play it with a Mpeg2 player. It just doesn't work.|||
I think upward compatibility doesn't work.
|||Why would you be passing around databases between in sql2000 and sql2005 in the first place? Detaching, moving, and attaching a database is a fairly rare occurrence to us.|||
JonM wrote:
Why would you be passing around databases between in sql2000 and sql2005 in the first place? Detaching, moving, and attaching a database is a fairly rare occurrence to us.
Jon,
With all due respect, what's it matter the reason for doing so? Whether it's a rare occurance or not, it's still a known issue that obviously many people have a problem with.
Now, you asked for a reason, so here's my scenerio.
I had a database driven website designed by an outside company, to be hosted by myself internally. The company that designed the site designed the DB in 2005 while I have SQL 2000.
Do you have any comments or resolution that may be of assistance to me / us?
Thank you.
Chris
|||reason 1
because the host provider has stated there is a problem with your database. You do not have a local copy. They take you off line and tell you to fix it and send you a 2005 mbf file.....You only have sql 2003
|||It sounds like you mainly want to perform maintenance or troubleshoot your sql server 2005 database and then send it back to your webhost that will run in it production. With this in mind I would recommend the following options:
1. Download the SQL Server 2005 Express Edition with Advanced Tools.
It includes the sql management studio which you can use to attach, detach, and manipulate your sql 2005 databases.
2. Buy a copy of SQL Server 2005 Developer Edition
This is a fairly cheap version of SQL Server and it has the functionality of enterprise edition. It is perfect for developing, troubleshooting and testing. It is also available in most MSDN Subscription levels. However, if you are only using the OLTP databse (which many of us are), I would simply recommend Express Edition.
3. Ask your webdesigner to migrate it to SQL Server 2000
If SQL 2000 is a design requirement, ask them if they could convert it over for you. It should not be that difficult, unless we are talking about a massive web application with hundreds of stored procedures.
|||I've loaded the sql server 2005 express, I do have the sql 2005 server but I have to figure out how to run install with a script as I have 2000 on my machine.....
I can not figure out how to run a maintenance using this express version to save my life....Is anyone willing to give me a hand? I sure would apprieciate it.
Error on Attaching Database
When attaching a database that was detached from another SQL Server instance.
I got the error message below:
Error 602: Could not find row in sysindexes for database ID 25, object ID 1,
index ID 1. Run DBCC CHECKTABLE on sysindexes.
i am using SQL Server 2000
Thanks and Regards
Was the database you attached from a SQL Server 2005 server? I get that error if I attach a 2005 database to a 2000 SQL Server.I don't know at this time thought if we are suppose to be able to attach a SQL 2005 database to a SQL 2000 server even if we keep it compatable.|||I also get this error when detaching a database from SQL Server 2005 and attaching to SQL Server 2000. Not sure what Microsoft's recommendation is or how to determine what might have changed in the schema to make it no longer compatible with SQL Server 2000.|||
I just hope somebody would help solve this prob coz i do have the same prob.
I can't attach a database from sql2005 back to sql2000 and it's giving me a lot of headache!
I got loads of work to do and this prob is eating my time.
Help!
|||You can't attach a 2005 database to 2000. The best you can do here is to export the data from the 2005 database and import into a 2000 database.|||It's not possible to take a sql2k5 database and attach it to sql2k. The meta data has changed drasticly on sql2k5. The change cannot be understood by sql2k.Your only option is to export/import to transfer data between the versions.|||You cannot attach a SQL Server 2005 database to SQL Server 2000 - even if this used to be a SQL Server 2000 database attached to SQL Server 2005 and attaching it back to SQL Server 2000. SQL Server 2005 changes some system objects which SQL Server 2000 does not have.|||If this is the case what is the reason for the compatability level. When I run sp_dbcmptlevel 'database' I get an 80, after I have made changes to the database with 2005 (80 is 2000, 90 is 2005). I was under the impression from a Microsoft person that this was something that could be done. I would like to do this incase we have major problems in Production after the upgrade to 2005. I have a lot of data in 50+ tables. import/Export would not be a good solution. Anyone from Microsoft care to chime in.|||Database compatibility has little to do with the changes in meta data. dbcmptlevel is set to allow sql2k5 to run the database at the current or lower settings.
This issue is very much not isolated. It's the same if you take a Mpeg4 file and try to play it with a Mpeg2 player. It just doesn't work.|||
I think upward compatibility doesn't work.
|||Why would you be passing around databases between in sql2000 and sql2005 in the first place? Detaching, moving, and attaching a database is a fairly rare occurrence to us.|||
Why would you be passing around databases between in sql2000 and sql2005 in the first place? Detaching, moving, and attaching a database is a fairly rare occurrence to us.
Jon,
With all due respect, what's it matter the reason for doing so? Whether it's a rare occurance or not, it's still a known issue that obviously many people have a problem with.
Now, you asked for a reason, so here's my scenerio.
I had a database driven website designed by an outside company, to be hosted by myself internally. The company that designed the site designed the DB in 2005 while I have SQL 2000.
Do you have any comments or resolution that may be of assistance to me / us?
Thank you.
Chris
|||reason 1
because the host provider has stated there is a problem with your database. You do not have a local copy. They take you off line and tell you to fix it and send you a 2005 mbf file.....You only have sql 2003
|||It sounds like you mainly want to perform maintenance or troubleshoot your sql server 2005 database and then send it back to your webhost that will run in it production. With this in mind I would recommend the following options:
1. Download the SQL Server 2005 Express Edition with Advanced Tools.
It includes the sql management studio which you can use to attach, detach, and manipulate your sql 2005 databases.
2. Buy a copy of SQL Server 2005 Developer Edition
This is a fairly cheap version of SQL Server and it has the functionality of enterprise edition. It is perfect for developing, troubleshooting and testing. It is also available in most MSDN Subscription levels. However, if you are only using the OLTP databse (which many of us are), I would simply recommend Express Edition.
3. Ask your webdesigner to migrate it to SQL Server 2000
If SQL 2000 is a design requirement, ask them if they could convert it over for you. It should not be that difficult, unless we are talking about a massive web application with hundreds of stored procedures.
|||I've loaded the sql server 2005 express, I do have the sql 2005 server but I have to figure out how to run install with a script as I have 2000 on my machine.....
I can not figure out how to run a maintenance using this express version to save my life....Is anyone willing to give me a hand? I sure would apprieciate it.
Error on Attaching Database
When attaching a database that was detached from another SQL Server instance.
I got the error message below:
Error 602: Could not find row in sysindexes for database ID 25, object ID 1,
index ID 1. Run DBCC CHECKTABLE on sysindexes.
i am using SQL Server 2000
Thanks and Regards
Was the database you attached from a SQL Server 2005 server? I get that error if I attach a 2005 database to a 2000 SQL Server.I don't know at this time thought if we are suppose to be able to attach a SQL 2005 database to a SQL 2000 server even if we keep it compatable.|||I also get this error when detaching a database from SQL Server 2005 and attaching to SQL Server 2000. Not sure what Microsoft's recommendation is or how to determine what might have changed in the schema to make it no longer compatible with SQL Server 2000.|||
I just hope somebody would help solve this prob coz i do have the same prob.
I can't attach a database from sql2005 back to sql2000 and it's giving me a lot of headache!
I got loads of work to do and this prob is eating my time.
Help!
|||You can't attach a 2005 database to 2000. The best you can do here is to export the data from the 2005 database and import into a 2000 database.|||It's not possible to take a sql2k5 database and attach it to sql2k. The meta data has changed drasticly on sql2k5. The change cannot be understood by sql2k.Your only option is to export/import to transfer data between the versions.|||You cannot attach a SQL Server 2005 database to SQL Server 2000 - even if this used to be a SQL Server 2000 database attached to SQL Server 2005 and attaching it back to SQL Server 2000. SQL Server 2005 changes some system objects which SQL Server 2000 does not have.|||If this is the case what is the reason for the compatability level. When I run sp_dbcmptlevel 'database' I get an 80, after I have made changes to the database with 2005 (80 is 2000, 90 is 2005). I was under the impression from a Microsoft person that this was something that could be done. I would like to do this incase we have major problems in Production after the upgrade to 2005. I have a lot of data in 50+ tables. import/Export would not be a good solution. Anyone from Microsoft care to chime in.|||Database compatibility has little to do with the changes in meta data. dbcmptlevel is set to allow sql2k5 to run the database at the current or lower settings.
This issue is very much not isolated. It's the same if you take a Mpeg4 file and try to play it with a Mpeg2 player. It just doesn't work.|||
I think upward compatibility doesn't work.
|||Why would you be passing around databases between in sql2000 and sql2005 in the first place? Detaching, moving, and attaching a database is a fairly rare occurrence to us.|||
JonM wrote:
Why would you be passing around databases between in sql2000 and sql2005 in the first place? Detaching, moving, and attaching a database is a fairly rare occurrence to us.
Jon,
With all due respect, what's it matter the reason for doing so? Whether it's a rare occurance or not, it's still a known issue that obviously many people have a problem with.
Now, you asked for a reason, so here's my scenerio.
I had a database driven website designed by an outside company, to be hosted by myself internally. The company that designed the site designed the DB in 2005 while I have SQL 2000.
Do you have any comments or resolution that may be of assistance to me / us?
Thank you.
Chris
|||reason 1
because the host provider has stated there is a problem with your database. You do not have a local copy. They take you off line and tell you to fix it and send you a 2005 mbf file.....You only have sql 2003
|||It sounds like you mainly want to perform maintenance or troubleshoot your sql server 2005 database and then send it back to your webhost that will run in it production. With this in mind I would recommend the following options:
1. Download the SQL Server 2005 Express Edition with Advanced Tools.
It includes the sql management studio which you can use to attach, detach, and manipulate your sql 2005 databases.
2. Buy a copy of SQL Server 2005 Developer Edition
This is a fairly cheap version of SQL Server and it has the functionality of enterprise edition. It is perfect for developing, troubleshooting and testing. It is also available in most MSDN Subscription levels. However, if you are only using the OLTP databse (which many of us are), I would simply recommend Express Edition.
3. Ask your webdesigner to migrate it to SQL Server 2000
If SQL 2000 is a design requirement, ask them if they could convert it over for you. It should not be that difficult, unless we are talking about a massive web application with hundreds of stored procedures.
|||I've loaded the sql server 2005 express, I do have the sql 2005 server but I have to figure out how to run install with a script as I have 2000 on my machine.....
I can not figure out how to run a maintenance using this express version to save my life....Is anyone willing to give me a hand? I sure would apprieciate it.
Error on Attaching Database
When attaching a database that was detached from another SQL Server instance.
I got the error message below:
Error 602: Could not find row in sysindexes for database ID 25, object ID 1,
index ID 1. Run DBCC CHECKTABLE on sysindexes.
i am using SQL Server 2000
Thanks and Regards
Was the database you attached from a SQL Server 2005 server? I get that error if I attach a 2005 database to a 2000 SQL Server.I don't know at this time thought if we are suppose to be able to attach a SQL 2005 database to a SQL 2000 server even if we keep it compatable.|||I also get this error when detaching a database from SQL Server 2005 and attaching to SQL Server 2000. Not sure what Microsoft's recommendation is or how to determine what might have changed in the schema to make it no longer compatible with SQL Server 2000.|||
I just hope somebody would help solve this prob coz i do have the same prob.
I can't attach a database from sql2005 back to sql2000 and it's giving me a lot of headache!
I got loads of work to do and this prob is eating my time.
Help!
|||You can't attach a 2005 database to 2000. The best you can do here is to export the data from the 2005 database and import into a 2000 database.|||It's not possible to take a sql2k5 database and attach it to sql2k. The meta data has changed drasticly on sql2k5. The change cannot be understood by sql2k.Your only option is to export/import to transfer data between the versions.|||You cannot attach a SQL Server 2005 database to SQL Server 2000 - even if this used to be a SQL Server 2000 database attached to SQL Server 2005 and attaching it back to SQL Server 2000. SQL Server 2005 changes some system objects which SQL Server 2000 does not have.|||If this is the case what is the reason for the compatability level. When I run sp_dbcmptlevel 'database' I get an 80, after I have made changes to the database with 2005 (80 is 2000, 90 is 2005). I was under the impression from a Microsoft person that this was something that could be done. I would like to do this incase we have major problems in Production after the upgrade to 2005. I have a lot of data in 50+ tables. import/Export would not be a good solution. Anyone from Microsoft care to chime in.|||Database compatibility has little to do with the changes in meta data. dbcmptlevel is set to allow sql2k5 to run the database at the current or lower settings.
This issue is very much not isolated. It's the same if you take a Mpeg4 file and try to play it with a Mpeg2 player. It just doesn't work.|||
I think upward compatibility doesn't work.
Why would you be passing around databases between in sql2000 and sql2005 in the first place? Detaching, moving, and attaching a database is a fairly rare occurrence to us.
Jon,
With all due respect, what's it matter the reason for doing so? Whether it's a rare occurance or not, it's still a known issue that obviously many people have a problem with.
Now, you asked for a reason, so here's my scenerio.
I had a database driven website designed by an outside company, to be hosted by myself internally. The company that designed the site designed the DB in 2005 while I have SQL 2000.
Do you have any comments or resolution that may be of assistance to me / us?
Thank you.
Chris
|||reason 1
because the host provider has stated there is a problem with your database. You do not have a local copy. They take you off line and tell you to fix it and send you a 2005 mbf file.....You only have sql 2003
|||It sounds like you mainly want to perform maintenance or troubleshoot your sql server 2005 database and then send it back to your webhost that will run in it production. With this in mind I would recommend the following options:
1. Download the SQL Server 2005 Express Edition with Advanced Tools.
It includes the sql management studio which you can use to attach, detach, and manipulate your sql 2005 databases.
2. Buy a copy of SQL Server 2005 Developer Edition
This is a fairly cheap version of SQL Server and it has the functionality of enterprise edition. It is perfect for developing, troubleshooting and testing. It is also available in most MSDN Subscription levels. However, if you are only using the OLTP databse (which many of us are), I would simply recommend Express Edition.
3. Ask your webdesigner to migrate it to SQL Server 2000
If SQL 2000 is a design requirement, ask them if they could convert it over for you. It should not be that difficult, unless we are talking about a massive web application with hundreds of stored procedures.
|||I've loaded the sql server 2005 express, I do have the sql 2005 server but I have to figure out how to run install with a script as I have 2000 on my machine.....
I can not figure out how to run a maintenance using this express version to save my life....Is anyone willing to give me a hand? I sure would apprieciate it.
Error on Attaching Database
When attaching a database that was detached from another SQL Server instance.
I got the error message below:
Error 602: Could not find row in sysindexes for database ID 25, object ID 1,
index ID 1. Run DBCC CHECKTABLE on sysindexes.
i am using SQL Server 2000
Thanks and Regards
Was the database you attached from a SQL Server 2005 server? I get that error if I attach a 2005 database to a 2000 SQL Server.I don't know at this time thought if we are suppose to be able to attach a SQL 2005 database to a SQL 2000 server even if we keep it compatable.|||I also get this error when detaching a database from SQL Server 2005 and attaching to SQL Server 2000. Not sure what Microsoft's recommendation is or how to determine what might have changed in the schema to make it no longer compatible with SQL Server 2000.|||
I just hope somebody would help solve this prob coz i do have the same prob.
I can't attach a database from sql2005 back to sql2000 and it's giving me a lot of headache!
I got loads of work to do and this prob is eating my time.
Help!
|||You can't attach a 2005 database to 2000. The best you can do here is to export the data from the 2005 database and import into a 2000 database.|||It's not possible to take a sql2k5 database and attach it to sql2k. The meta data has changed drasticly on sql2k5. The change cannot be understood by sql2k.Your only option is to export/import to transfer data between the versions.|||You cannot attach a SQL Server 2005 database to SQL Server 2000 - even if this used to be a SQL Server 2000 database attached to SQL Server 2005 and attaching it back to SQL Server 2000. SQL Server 2005 changes some system objects which SQL Server 2000 does not have.|||If this is the case what is the reason for the compatability level. When I run sp_dbcmptlevel 'database' I get an 80, after I have made changes to the database with 2005 (80 is 2000, 90 is 2005). I was under the impression from a Microsoft person that this was something that could be done. I would like to do this incase we have major problems in Production after the upgrade to 2005. I have a lot of data in 50+ tables. import/Export would not be a good solution. Anyone from Microsoft care to chime in.|||Database compatibility has little to do with the changes in meta data. dbcmptlevel is set to allow sql2k5 to run the database at the current or lower settings.
This issue is very much not isolated. It's the same if you take a Mpeg4 file and try to play it with a Mpeg2 player. It just doesn't work.|||
I think upward compatibility doesn't work.
Why would you be passing around databases between in sql2000 and sql2005 in the first place? Detaching, moving, and attaching a database is a fairly rare occurrence to us.
Jon,
With all due respect, what's it matter the reason for doing so? Whether it's a rare occurance or not, it's still a known issue that obviously many people have a problem with.
Now, you asked for a reason, so here's my scenerio.
I had a database driven website designed by an outside company, to be hosted by myself internally. The company that designed the site designed the DB in 2005 while I have SQL 2000.
Do you have any comments or resolution that may be of assistance to me / us?
Thank you.
Chris
|||reason 1
because the host provider has stated there is a problem with your database. You do not have a local copy. They take you off line and tell you to fix it and send you a 2005 mbf file.....You only have sql 2003
|||It sounds like you mainly want to perform maintenance or troubleshoot your sql server 2005 database and then send it back to your webhost that will run in it production. With this in mind I would recommend the following options:
1. Download the SQL Server 2005 Express Edition with Advanced Tools.
It includes the sql management studio which you can use to attach, detach, and manipulate your sql 2005 databases.
2. Buy a copy of SQL Server 2005 Developer Edition
This is a fairly cheap version of SQL Server and it has the functionality of enterprise edition. It is perfect for developing, troubleshooting and testing. It is also available in most MSDN Subscription levels. However, if you are only using the OLTP databse (which many of us are), I would simply recommend Express Edition.
3. Ask your webdesigner to migrate it to SQL Server 2000
If SQL 2000 is a design requirement, ask them if they could convert it over for you. It should not be that difficult, unless we are talking about a massive web application with hundreds of stored procedures.
|||I've loaded the sql server 2005 express, I do have the sql 2005 server but I have to figure out how to run install with a script as I have 2000 on my machine.....
I can not figure out how to run a maintenance using this express version to save my life....Is anyone willing to give me a hand? I sure would apprieciate it.
Error on Attaching Database
When attaching a database that was detached from another SQL Server instance.
I got the error message below:
Error 602: Could not find row in sysindexes for database ID 25, object ID 1,
index ID 1. Run DBCC CHECKTABLE on sysindexes.
i am using SQL Server 2000
Thanks and Regards
Was the database you attached from a SQL Server 2005 server? I get that error if I attach a 2005 database to a 2000 SQL Server.I don't know at this time thought if we are suppose to be able to attach a SQL 2005 database to a SQL 2000 server even if we keep it compatable.|||I also get this error when detaching a database from SQL Server 2005 and attaching to SQL Server 2000. Not sure what Microsoft's recommendation is or how to determine what might have changed in the schema to make it no longer compatible with SQL Server 2000.|||
I just hope somebody would help solve this prob coz i do have the same prob.
I can't attach a database from sql2005 back to sql2000 and it's giving me a lot of headache!
I got loads of work to do and this prob is eating my time.
Help!
|||You can't attach a 2005 database to 2000. The best you can do here is to export the data from the 2005 database and import into a 2000 database.|||It's not possible to take a sql2k5 database and attach it to sql2k. The meta data has changed drasticly on sql2k5. The change cannot be understood by sql2k.Your only option is to export/import to transfer data between the versions.|||You cannot attach a SQL Server 2005 database to SQL Server 2000 - even if this used to be a SQL Server 2000 database attached to SQL Server 2005 and attaching it back to SQL Server 2000. SQL Server 2005 changes some system objects which SQL Server 2000 does not have.|||If this is the case what is the reason for the compatability level. When I run sp_dbcmptlevel 'database' I get an 80, after I have made changes to the database with 2005 (80 is 2000, 90 is 2005). I was under the impression from a Microsoft person that this was something that could be done. I would like to do this incase we have major problems in Production after the upgrade to 2005. I have a lot of data in 50+ tables. import/Export would not be a good solution. Anyone from Microsoft care to chime in.|||Database compatibility has little to do with the changes in meta data. dbcmptlevel is set to allow sql2k5 to run the database at the current or lower settings.
This issue is very much not isolated. It's the same if you take a Mpeg4 file and try to play it with a Mpeg2 player. It just doesn't work.|||
I think upward compatibility doesn't work.
Why would you be passing around databases between in sql2000 and sql2005 in the first place? Detaching, moving, and attaching a database is a fairly rare occurrence to us.
Jon,
With all due respect, what's it matter the reason for doing so? Whether it's a rare occurance or not, it's still a known issue that obviously many people have a problem with.
Now, you asked for a reason, so here's my scenerio.
I had a database driven website designed by an outside company, to be hosted by myself internally. The company that designed the site designed the DB in 2005 while I have SQL 2000.
Do you have any comments or resolution that may be of assistance to me / us?
Thank you.
Chris
|||reason 1
because the host provider has stated there is a problem with your database. You do not have a local copy. They take you off line and tell you to fix it and send you a 2005 mbf file.....You only have sql 2003
|||It sounds like you mainly want to perform maintenance or troubleshoot your sql server 2005 database and then send it back to your webhost that will run in it production. With this in mind I would recommend the following options:
1. Download the SQL Server 2005 Express Edition with Advanced Tools.
It includes the sql management studio which you can use to attach, detach, and manipulate your sql 2005 databases.
2. Buy a copy of SQL Server 2005 Developer Edition
This is a fairly cheap version of SQL Server and it has the functionality of enterprise edition. It is perfect for developing, troubleshooting and testing. It is also available in most MSDN Subscription levels. However, if you are only using the OLTP databse (which many of us are), I would simply recommend Express Edition.
3. Ask your webdesigner to migrate it to SQL Server 2000
If SQL 2000 is a design requirement, ask them if they could convert it over for you. It should not be that difficult, unless we are talking about a massive web application with hundreds of stored procedures.
|||I've loaded the sql server 2005 express, I do have the sql 2005 server but I have to figure out how to run install with a script as I have 2000 on my machine.....
I can not figure out how to run a maintenance using this express version to save my life....Is anyone willing to give me a hand? I sure would apprieciate it.
Error on Attaching Database
When attaching a database that was detached from another SQL Server instance.
I got the error message below:
Error 602: Could not find row in sysindexes for database ID 25, object ID 1,
index ID 1. Run DBCC CHECKTABLE on sysindexes.
i am using SQL Server 2000
Thanks and Regards
Was the database you attached from a SQL Server 2005 server? I get that error if I attach a 2005 database to a 2000 SQL Server.I don't know at this time thought if we are suppose to be able to attach a SQL 2005 database to a SQL 2000 server even if we keep it compatable.|||I also get this error when detaching a database from SQL Server 2005 and attaching to SQL Server 2000. Not sure what Microsoft's recommendation is or how to determine what might have changed in the schema to make it no longer compatible with SQL Server 2000.|||
I just hope somebody would help solve this prob coz i do have the same prob.
I can't attach a database from sql2005 back to sql2000 and it's giving me a lot of headache!
I got loads of work to do and this prob is eating my time.
Help!
|||You can't attach a 2005 database to 2000. The best you can do here is to export the data from the 2005 database and import into a 2000 database.|||It's not possible to take a sql2k5 database and attach it to sql2k. The meta data has changed drasticly on sql2k5. The change cannot be understood by sql2k.Your only option is to export/import to transfer data between the versions.|||You cannot attach a SQL Server 2005 database to SQL Server 2000 - even if this used to be a SQL Server 2000 database attached to SQL Server 2005 and attaching it back to SQL Server 2000. SQL Server 2005 changes some system objects which SQL Server 2000 does not have.|||If this is the case what is the reason for the compatability level. When I run sp_dbcmptlevel 'database' I get an 80, after I have made changes to the database with 2005 (80 is 2000, 90 is 2005). I was under the impression from a Microsoft person that this was something that could be done. I would like to do this incase we have major problems in Production after the upgrade to 2005. I have a lot of data in 50+ tables. import/Export would not be a good solution. Anyone from Microsoft care to chime in.|||Database compatibility has little to do with the changes in meta data. dbcmptlevel is set to allow sql2k5 to run the database at the current or lower settings.
This issue is very much not isolated. It's the same if you take a Mpeg4 file and try to play it with a Mpeg2 player. It just doesn't work.|||
I think upward compatibility doesn't work.
|||Why would you be passing around databases between in sql2000 and sql2005 in the first place? Detaching, moving, and attaching a database is a fairly rare occurrence to us.|||
Why would you be passing around databases between in sql2000 and sql2005 in the first place? Detaching, moving, and attaching a database is a fairly rare occurrence to us.
Jon,
With all due respect, what's it matter the reason for doing so? Whether it's a rare occurance or not, it's still a known issue that obviously many people have a problem with.
Now, you asked for a reason, so here's my scenerio.
I had a database driven website designed by an outside company, to be hosted by myself internally. The company that designed the site designed the DB in 2005 while I have SQL 2000.
Do you have any comments or resolution that may be of assistance to me / us?
Thank you.
Chris
|||reason 1
because the host provider has stated there is a problem with your database. You do not have a local copy. They take you off line and tell you to fix it and send you a 2005 mbf file.....You only have sql 2003
|||It sounds like you mainly want to perform maintenance or troubleshoot your sql server 2005 database and then send it back to your webhost that will run in it production. With this in mind I would recommend the following options:
1. Download the SQL Server 2005 Express Edition with Advanced Tools.
It includes the sql management studio which you can use to attach, detach, and manipulate your sql 2005 databases.
2. Buy a copy of SQL Server 2005 Developer Edition
This is a fairly cheap version of SQL Server and it has the functionality of enterprise edition. It is perfect for developing, troubleshooting and testing. It is also available in most MSDN Subscription levels. However, if you are only using the OLTP databse (which many of us are), I would simply recommend Express Edition.
3. Ask your webdesigner to migrate it to SQL Server 2000
If SQL 2000 is a design requirement, ask them if they could convert it over for you. It should not be that difficult, unless we are talking about a massive web application with hundreds of stored procedures.
|||I've loaded the sql server 2005 express, I do have the sql 2005 server but I have to figure out how to run install with a script as I have 2000 on my machine.....
I can not figure out how to run a maintenance using this express version to save my life....Is anyone willing to give me a hand? I sure would apprieciate it.
Error on Attaching Database
When attaching a database that was detached from another SQL Server instance.
I got the error message below:
Error 602: Could not find row in sysindexes for database ID 25, object ID 1,
index ID 1. Run DBCC CHECKTABLE on sysindexes.
i am using SQL Server 2000
Thanks and Regards
Was the database you attached from a SQL Server 2005 server? I get that error if I attach a 2005 database to a 2000 SQL Server.I don't know at this time thought if we are suppose to be able to attach a SQL 2005 database to a SQL 2000 server even if we keep it compatable.|||I also get this error when detaching a database from SQL Server 2005 and attaching to SQL Server 2000. Not sure what Microsoft's recommendation is or how to determine what might have changed in the schema to make it no longer compatible with SQL Server 2000.|||
I just hope somebody would help solve this prob coz i do have the same prob.
I can't attach a database from sql2005 back to sql2000 and it's giving me a lot of headache!
I got loads of work to do and this prob is eating my time.
Help!
|||You can't attach a 2005 database to 2000. The best you can do here is to export the data from the 2005 database and import into a 2000 database.|||It's not possible to take a sql2k5 database and attach it to sql2k. The meta data has changed drasticly on sql2k5. The change cannot be understood by sql2k.Your only option is to export/import to transfer data between the versions.|||You cannot attach a SQL Server 2005 database to SQL Server 2000 - even if this used to be a SQL Server 2000 database attached to SQL Server 2005 and attaching it back to SQL Server 2000. SQL Server 2005 changes some system objects which SQL Server 2000 does not have.|||If this is the case what is the reason for the compatability level. When I run sp_dbcmptlevel 'database' I get an 80, after I have made changes to the database with 2005 (80 is 2000, 90 is 2005). I was under the impression from a Microsoft person that this was something that could be done. I would like to do this incase we have major problems in Production after the upgrade to 2005. I have a lot of data in 50+ tables. import/Export would not be a good solution. Anyone from Microsoft care to chime in.|||Database compatibility has little to do with the changes in meta data. dbcmptlevel is set to allow sql2k5 to run the database at the current or lower settings.
This issue is very much not isolated. It's the same if you take a Mpeg4 file and try to play it with a Mpeg2 player. It just doesn't work.|||
I think upward compatibility doesn't work.
|||Why would you be passing around databases between in sql2000 and sql2005 in the first place? Detaching, moving, and attaching a database is a fairly rare occurrence to us.|||
Why would you be passing around databases between in sql2000 and sql2005 in the first place? Detaching, moving, and attaching a database is a fairly rare occurrence to us.
Jon,
With all due respect, what's it matter the reason for doing so? Whether it's a rare occurance or not, it's still a known issue that obviously many people have a problem with.
Now, you asked for a reason, so here's my scenerio.
I had a database driven website designed by an outside company, to be hosted by myself internally. The company that designed the site designed the DB in 2005 while I have SQL 2000.
Do you have any comments or resolution that may be of assistance to me / us?
Thank you.
Chris
|||reason 1
because the host provider has stated there is a problem with your database. You do not have a local copy. They take you off line and tell you to fix it and send you a 2005 mbf file.....You only have sql 2003
|||It sounds like you mainly want to perform maintenance or troubleshoot your sql server 2005 database and then send it back to your webhost that will run in it production. With this in mind I would recommend the following options:
1. Download the SQL Server 2005 Express Edition with Advanced Tools.
It includes the sql management studio which you can use to attach, detach, and manipulate your sql 2005 databases.
2. Buy a copy of SQL Server 2005 Developer Edition
This is a fairly cheap version of SQL Server and it has the functionality of enterprise edition. It is perfect for developing, troubleshooting and testing. It is also available in most MSDN Subscription levels. However, if you are only using the OLTP databse (which many of us are), I would simply recommend Express Edition.
3. Ask your webdesigner to migrate it to SQL Server 2000
If SQL 2000 is a design requirement, ask them if they could convert it over for you. It should not be that difficult, unless we are talking about a massive web application with hundreds of stored procedures.
|||I've loaded the sql server 2005 express, I do have the sql 2005 server but I have to figure out how to run install with a script as I have 2000 on my machine.....
I can not figure out how to run a maintenance using this express version to save my life....Is anyone willing to give me a hand? I sure would apprieciate it.
Error on attaching a database
When attaching a database that was detached from another SQL Server instance(copied raw .mdf and ldf files)..
I got the error message below:
Error 602: Could not find row in sysindexes for database ID 25, object ID 1,
index ID 1. Run DBCC CHECKTABLE on sysindexes.
how can i solve this problem. i am using SQL Server 2000
Thanks and Regards
hi,
Could you be more specific. How did you detached the your database? Did you do it by backup and restore or copy the .mdf and .ldf file and attached.
Michael Castillones
|||hai oblax77
I copied raw .mdf and ldf files.
Regards
|||
hi,
Maybe your database was corrupted because the errors includes the system indexes already.
Error on attaching a database
When attaching a database that was detached from another SQL Server instance(copied raw .mdf and ldf files)..
I got the error message below:
Error 602: Could not find row in sysindexes for database ID 25, object ID 1,
index ID 1. Run DBCC CHECKTABLE on sysindexes.
how can i solve this problem. i am using SQL Server 2000
Thanks and Regards
hi,
Could you be more specific. How did you detached the your database? Did you do it by backup and restore or copy the .mdf and .ldf file and attached.
Michael Castillones
|||hai oblax77
I copied raw .mdf and ldf files.
Regards
|||
hi,
Maybe your database was corrupted because the errors includes the system indexes already.
Friday, March 9, 2012
Error msg when installing
When I try to run MSDE setup, i get a msg (after a msg about starting to
configure) roughly like this: "...instance name is invalid" - how come?
Very grateful for help!
Hi,
Try running the setup from command line to install the MSDE.
1. Run command prompt.
2. Change the directory to the MSDE install extract folder
3. Run the following command:
setup.exe INSTANCENAME="testmsde" DISABLEROLLBACK=1 SAPWD="password" /L*v
c:\temp\setup.log
Thanks
Hari
"Black Eagle" <BlackEagle@.discussions.microsoft.com> wrote in message
news:F0709E51-93C5-42D3-98B6-DB32FB7B0127@.microsoft.com...
> When I try to run MSDE setup, i get a msg (after a msg about starting to
> configure) roughly like this: "...instance name is invalid" - how come?
> Very grateful for help!
>
configure) roughly like this: "...instance name is invalid" - how come?
Very grateful for help!
Hi,
Try running the setup from command line to install the MSDE.
1. Run command prompt.
2. Change the directory to the MSDE install extract folder
3. Run the following command:
setup.exe INSTANCENAME="testmsde" DISABLEROLLBACK=1 SAPWD="password" /L*v
c:\temp\setup.log
Thanks
Hari
"Black Eagle" <BlackEagle@.discussions.microsoft.com> wrote in message
news:F0709E51-93C5-42D3-98B6-DB32FB7B0127@.microsoft.com...
> When I try to run MSDE setup, i get a msg (after a msg about starting to
> configure) roughly like this: "...instance name is invalid" - how come?
> Very grateful for help!
>
Sunday, February 26, 2012
Error Message when trying to open AdventureWorksDB in vbexpress
I get the following error message when trying to open the AdventureWordsDB in VBExpress: "Failed to generate a user instance of SQL Server dut to failure in starting the process for the user instance. The connection will be closed." Can someone tell me what the problem is and how to solve it? Thanks, Ray Holt
hi,
you seemed to open a database in User Instace mode.. User Instances are available in SQLExpress edition only and they have to be enabled.. at installation time of SQLExpress a kind of message asks you to enable this feature or not, but you can enable it even later executing the sp_configure system stored procedure with the 'user instances enabled' parameter..
regards
|||How do I execute the sp_configure? Thanks, Ray Holt|||hi Ray,
for your convenience, you can download and install SQL Server Management Studio Express... you can then execute it, "open a new query", and execute the sp_configure call..
regards
Error Message When Connecting to SQl Server Data
I am using MSDE on XP pro Service Pack 2 and have stored my data on the
default instance of MSSQLSERVER on my computer ID OFFICEPC. This is
networked to LAPTOP and SHOPPC.
My Access front end works fine with the SQL back end on the OFFICEPC. But
when I try to link the same front end from one of the other computers using
ODBC, i get the following error:
Connection Failed:
SQL state 2800
SQL Server Error 18456
[Microsoft][ODBC SQL Server Driver][SQL Server] Login failed for user
'OFFICEPC\Guest'
I have run svrnetcn.exe and enabled port 1433 to pass through the firewall.
Ports 135 and 445 are also enabled.
What have I done wrong? Thanks in advance for any help
hi Gerald,
"Gerald G" <GeraldG@.discussions.microsoft.com> ha scritto nel messaggio
news:54F59F97-F083-4C93-B08A-4FCEA3429731@.microsoft.com
> I am using MSDE on XP pro Service Pack 2 and have stored my data on
> the default instance of MSSQLSERVER on my computer ID OFFICEPC. This
> is networked to LAPTOP and SHOPPC.
> My Access front end works fine with the SQL back end on the OFFICEPC.
> But when I try to link the same front end from one of the other
> computers using ODBC, i get the following error:
> Connection Failed:
> SQL state 2800
> SQL Server Error 18456
> [Microsoft][ODBC SQL Server Driver][SQL Server] Login failed for user
> 'OFFICEPC\Guest'
> I have run svrnetcn.exe and enabled port 1433 to pass through the
> firewall. Ports 135 and 445 are also enabled.
> What have I done wrong? Thanks in advance for any help
it seems you do not have firewall troubles, but standard security problems,
as OFFICEPC\.. users are not granted login to MSDE instance... please verify
your Logins
can you telnet on port 1433 the MSDE instance?
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hi Andrea - thanks for answering
I think you are right about it being a standard security problem. How do I
telnet on port 1433, and How do I grant login to my MSDE instance?
"Andrea Montanari" wrote:
> hi Gerald,
> "Gerald G" <GeraldG@.discussions.microsoft.com> ha scritto nel messaggio
> news:54F59F97-F083-4C93-B08A-4FCEA3429731@.microsoft.com
> it seems you do not have firewall troubles, but standard security problems,
> as OFFICEPC\.. users are not granted login to MSDE instance... please verify
> your Logins
> can you telnet on port 1433 the MSDE instance?
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||hi Gerald
"Gerald G" <GeraldG@.discussions.microsoft.com> ha scritto nel messaggio
news:7CD6EC0F-53A4-4252-9228-A40089BE66FF@.microsoft.com
> Hi Andrea - thanks for answering
> I think you are right about it being a standard security problem.
> How do I telnet on port 1433, and How do I grant login to my MSDE
> instance?
>
in order to grant your 'OFFICEPC\xxxx' users, you have to add them to the
SQL Server Windows logins...
please have a look at
http://support.microsoft.com/default...N-US;q325003#8 for
further info about granting login to Windows logins/groups
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
default instance of MSSQLSERVER on my computer ID OFFICEPC. This is
networked to LAPTOP and SHOPPC.
My Access front end works fine with the SQL back end on the OFFICEPC. But
when I try to link the same front end from one of the other computers using
ODBC, i get the following error:
Connection Failed:
SQL state 2800
SQL Server Error 18456
[Microsoft][ODBC SQL Server Driver][SQL Server] Login failed for user
'OFFICEPC\Guest'
I have run svrnetcn.exe and enabled port 1433 to pass through the firewall.
Ports 135 and 445 are also enabled.
What have I done wrong? Thanks in advance for any help
hi Gerald,
"Gerald G" <GeraldG@.discussions.microsoft.com> ha scritto nel messaggio
news:54F59F97-F083-4C93-B08A-4FCEA3429731@.microsoft.com
> I am using MSDE on XP pro Service Pack 2 and have stored my data on
> the default instance of MSSQLSERVER on my computer ID OFFICEPC. This
> is networked to LAPTOP and SHOPPC.
> My Access front end works fine with the SQL back end on the OFFICEPC.
> But when I try to link the same front end from one of the other
> computers using ODBC, i get the following error:
> Connection Failed:
> SQL state 2800
> SQL Server Error 18456
> [Microsoft][ODBC SQL Server Driver][SQL Server] Login failed for user
> 'OFFICEPC\Guest'
> I have run svrnetcn.exe and enabled port 1433 to pass through the
> firewall. Ports 135 and 445 are also enabled.
> What have I done wrong? Thanks in advance for any help
it seems you do not have firewall troubles, but standard security problems,
as OFFICEPC\.. users are not granted login to MSDE instance... please verify
your Logins
can you telnet on port 1433 the MSDE instance?
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hi Andrea - thanks for answering
I think you are right about it being a standard security problem. How do I
telnet on port 1433, and How do I grant login to my MSDE instance?
"Andrea Montanari" wrote:
> hi Gerald,
> "Gerald G" <GeraldG@.discussions.microsoft.com> ha scritto nel messaggio
> news:54F59F97-F083-4C93-B08A-4FCEA3429731@.microsoft.com
> it seems you do not have firewall troubles, but standard security problems,
> as OFFICEPC\.. users are not granted login to MSDE instance... please verify
> your Logins
> can you telnet on port 1433 the MSDE instance?
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||hi Gerald
"Gerald G" <GeraldG@.discussions.microsoft.com> ha scritto nel messaggio
news:7CD6EC0F-53A4-4252-9228-A40089BE66FF@.microsoft.com
> Hi Andrea - thanks for answering
> I think you are right about it being a standard security problem.
> How do I telnet on port 1433, and How do I grant login to my MSDE
> instance?
>
in order to grant your 'OFFICEPC\xxxx' users, you have to add them to the
SQL Server Windows logins...
please have a look at
http://support.microsoft.com/default...N-US;q325003#8 for
further info about granting login to Windows logins/groups
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
Wednesday, February 15, 2012
error message
I am getting this error trying accessing RM page.
Server Error in '/Reports' Application.
----
Object reference not set to an instance of an object.
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information
about the error and where it originated in the code.
Exception Details: System.NullReferenceException: Object reference not set
to an instance of an object.
Source Error:
An unhandled exception was generated during the execution of the current web
request. Information regarding the origin and location of the exception can
be identified using the exception stack trace below.
Stack Trace:
[NullReferenceException: Object reference not set to an instance of an
object.]
Microsoft.ReportingServices.UI.GlobalApp.Application_AuthenticateRequest(Object
sender, EventArgs e) +58
System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
+92
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean&
completedSynchronously) +64
Any idea?
ThanksOn Aug 12, 8:53 pm, "markgoldin" <markgoldin_2...@.yahoo.com> wrote:
> I am getting this error trying accessing RM page.
> Server Error in '/Reports' Application.
> ----
> Object reference not set to an instance of an object.
> Description: An unhandled exception occurred during the execution of the
> current web request. Please review the stack trace for more information
> about the error and where it originated in the code.
> Exception Details: System.NullReferenceException: Object reference not set
> to an instance of an object.
> Source Error:
> An unhandled exception was generated during the execution of the current web
> request. Information regarding the origin and location of the exception can
> be identified using the exception stack trace below.
> Stack Trace:
> [NullReferenceException: Object reference not set to an instance of an
> object.]
> Microsoft.ReportingServices.UI.GlobalApp.Application_AuthenticateRequest(Object
> sender, EventArgs e) +58
> System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
> +92
> System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean&
> completedSynchronously) +64
> Any idea?
> Thanks
You should try looking in the SSRS logs to see if it gives you any
descriptive information (normally located in: C:\Program Files
\Microsoft SQL Server\MSSQL.2\Reporting Services\LogFiles ). If you
cannot resolve the issue by looking at the logs, you should look into
reinstalling SSRS. Hope this helps.
Regards,
Enrique Martinez
Sr. Software Consultant
Server Error in '/Reports' Application.
----
Object reference not set to an instance of an object.
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information
about the error and where it originated in the code.
Exception Details: System.NullReferenceException: Object reference not set
to an instance of an object.
Source Error:
An unhandled exception was generated during the execution of the current web
request. Information regarding the origin and location of the exception can
be identified using the exception stack trace below.
Stack Trace:
[NullReferenceException: Object reference not set to an instance of an
object.]
Microsoft.ReportingServices.UI.GlobalApp.Application_AuthenticateRequest(Object
sender, EventArgs e) +58
System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
+92
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean&
completedSynchronously) +64
Any idea?
ThanksOn Aug 12, 8:53 pm, "markgoldin" <markgoldin_2...@.yahoo.com> wrote:
> I am getting this error trying accessing RM page.
> Server Error in '/Reports' Application.
> ----
> Object reference not set to an instance of an object.
> Description: An unhandled exception occurred during the execution of the
> current web request. Please review the stack trace for more information
> about the error and where it originated in the code.
> Exception Details: System.NullReferenceException: Object reference not set
> to an instance of an object.
> Source Error:
> An unhandled exception was generated during the execution of the current web
> request. Information regarding the origin and location of the exception can
> be identified using the exception stack trace below.
> Stack Trace:
> [NullReferenceException: Object reference not set to an instance of an
> object.]
> Microsoft.ReportingServices.UI.GlobalApp.Application_AuthenticateRequest(Object
> sender, EventArgs e) +58
> System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
> +92
> System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean&
> completedSynchronously) +64
> Any idea?
> Thanks
You should try looking in the SSRS logs to see if it gives you any
descriptive information (normally located in: C:\Program Files
\Microsoft SQL Server\MSSQL.2\Reporting Services\LogFiles ). If you
cannot resolve the issue by looking at the logs, you should look into
reinstalling SSRS. Hope this helps.
Regards,
Enrique Martinez
Sr. Software Consultant
Subscribe to:
Posts (Atom)