Error Reporting service

hi
i am using SQL Server 2005 reporting services, i am getting an error message while deploying .rdl file error is:" Connection could not be established to remote server http://localhost/ReportServer"
Additional information is :
"client found response content type of text/html; charset=utf-8 but expected text/XML"Are you just trying to connect through the browser or to upload a file?|||Oh sorry I see. Are you able to connet to the instance through the browser?|||now its working properly, i have executed aspnet_regsql -ga aspnet commond on command prompt. But now while deploying i m getting another problem: "An internal error occurred on the report server. See the error log for more details."

Error Recieved While Reindexing

Folks
i recieved an error message while doing a reindex.
The error Message is
[dbo].[XX_TL_WRK109TBL]
[Microsoft][ODBC SQL Server Driver]Unknown token received from SQL Server
Connection Broken
The Command i used to reindex 'ALL' Tables is
EXEC sp_MSforeachtable @.command1="print '?' DBCC DBREINDEX ('?')"
We are still at Service pack 2 cos PeopleSoft has not certified Service Pack
3a yet.
We are running a Peoplesoft Application[posted and mailed, please reply in news]
examnotes (gwadhwani@.econsult.us) writes:

quote:

---

> Folks
> i recieved an error message while doing a reindex.
> The error Message is
> [dbo].[XX_TL_WRK109TBL]
> [Microsoft][ODBC SQL Server Driver]Unknown token received from SQL Server
> Connection Broken

---

That doesn't bode well.
While that error occasionally may indicate a true protocol error, it
most often means that SQL Server slammed the door in the face on
you and cut the connection. Not without reason: there was a fatal
error in the execution on the SQL Server side. If you check the SQL Server
errorlog you will probably find a stack dump there.
These kinds of errors are basically always bugs in SQL Server; you should
always get a decent error message back. But if you get this during
DBREINDEX, I'm getting nervous that you have corruption in your database.
So a DBCC CHECKDB would be in place.
Before you open a case with Microsoft, you may want try something
like:
SELECT 'DBCC DBREINDEX(' + name + ')' FROM sysobjects WHERE xtype = 'U'
to factor out sp_MSforeachdb which is undocumented and usage of
it is unsupported.
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

Error Recieved While Reindexing

Folk
i recieved an error message while doing a reindex
The error Message is
[dbo].[XX_TL_WRK109TBL
[Microsoft][ODBC SQL Server Driver]Unknown token received from SQL Serve
Connection Broke
The Command i used to reindex 'ALL' Tables is
EXEC sp_MSforeachtable @.command1="print '?' DBCC DBREINDEX ('?')
We are still at Service pack 2 cos PeopleSoft has not certified Service Pack 3a yet
We are running a Peoplesoft Application[posted and mailed, please reply in news]
=?Utf-8?B?R2lyaXNo?= (gwadhwani@.econsult.us) writes:
> Folks
> i recieved an error message while doing a reindex.
> The error Message is
> [dbo].[XX_TL_WRK109TBL]
> [Microsoft][ODBC SQL Server Driver]Unknown token received from SQL Server
> Connection Broken
That doesn't bode well.
While that error occasionally may indicate a true protocol error, it
most often means that SQL Server slammed the door in the face on
you and cut the connection. Not without reason: there was a fatal
error in the execution on the SQL Server side. If you check the SQL Server
errorlog you will probably find a stack dump there.
These kinds of errors are basically always bugs in SQL Server; you should
always get a decent error message back. But if you get this during
DBREINDEX, I'm getting nervous that you have corruption in your database.
So a DBCC CHECKDB would be in place.
Before you open a case with Microsoft, you may want try something
like:
SELECT 'DBCC DBREINDEX(' + name + ')' FROM sysobjects WHERE xtype = 'U'
to factor out sp_MSforeachdb which is undocumented and usage of
it is unsupported.
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp

Error Processing Dimensions

Hi,

I'm getting an error when processing a Dimension (translated from german):

Origin German Error Message:

Fehler im Back-End-Datenbankzugriffsmodul. OLE DB hat den unbekannten Status '' für die 1-Spalte gemeldet. Fehler im OLAP-Speichermodul: Fehler beim Verarbeiten des RATED CDR-Attributs der RATED CDR-Dimension aus der CubeTest2-Datenbank.

Translation:

Error in the Backend Data Access Module: OLE DB has returned the unknown Status '' for column 1. Error in the OLAP Storagemodule: Error in processing the rated_cdr Attribute of Rated_cdr dimension from CubeTest2 Database.

We're trying to read the Dimension Data from an IBM DB2 Database. All Access rights to the database are given to the running user.

I have no idea what the reason for this Problem could be.

Any ideas?

Thanks.

Ertan

Try and see if you can access data in DB2 through the BI Dev Studio DSV editor. Right click on the DSV table->Explore data.
This is going to test whether current user can access DB2 data through OLEDB provider.

After that you need to make sure Analysis Server's service account has the same privileges as the user accessed data from BI Dev Studio.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

Yes I can access the data through DSV. Also the AS Service account is the same as what is used in DSV.

The same Cube based on a SQL Server Database is not returning any Problems. Could it be a Problem with the DB2 OLE DB Driver itself?

Any other ideas?

Ertan

|||

Ertan,

I have the same errors, also using DB2. Did you get your problems fix? I can also browse data from table.

Rue

sql

error opening table in Enterprise MGR

I am getting an error message when I try to open (to view the rows of) any
table in any of the databases on a SQL 7 server from the server where the
databases actually reside- it says:
"An unexpected error happened during this operation. [Query] - Query
Designer encountered a query error: Unspecified error
This error is new; I am able to query and get results from the tables in
query analyzer and I am able to view the tables through Enterprise Manager
when I link to these databases from another computer. I restarted SQL server
without any luck. Do you think it needs to be reinstalled?
Check the following article which addresses the issue:
FIX: Enterprise Manager Returns Unexpected Error on Table or
View
http://support.microsoft.com/?id=273472
-Sue
On Wed, 26 Jan 2005 07:47:03 -0800, "PatW"
<PatW@.discussions.microsoft.com> wrote:

>I am getting an error message when I try to open (to view the rows of) any
>table in any of the databases on a SQL 7 server from the server where the
>databases actually reside- it says:
>"An unexpected error happened during this operation. [Query] - Query
>Designer encountered a query error: Unspecified error
>This error is new; I am able to query and get results from the tables in
>query analyzer and I am able to view the tables through Enterprise Manager
>when I link to these databases from another computer. I restarted SQL server
>without any luck. Do you think it needs to be reinstalled?
sql

error opening table in Enterprise MGR

I am getting an error message when I try to open (to view the rows of) any
table in any of the databases on a SQL 7 server from the server where the
databases actually reside- it says:
"An unexpected error happened during this operation. [Query] - Query
Designer encountered a query error: Unspecified error
This error is new; I am able to query and get results from the tables in
query analyzer and I am able to view the tables through Enterprise Manager
when I link to these databases from another computer. I restarted SQL serve
r
without any luck. Do you think it needs to be reinstalled?Check the following article which addresses the issue:
FIX: Enterprise Manager Returns Unexpected Error on Table or
View
http://support.microsoft.com/?id=273472
-Sue
On Wed, 26 Jan 2005 07:47:03 -0800, "PatW"
<PatW@.discussions.microsoft.com> wrote:

>I am getting an error message when I try to open (to view the rows of) any
>table in any of the databases on a SQL 7 server from the server where the
>databases actually reside- it says:
>"An unexpected error happened during this operation. [Query] - Query
>Designer encountered a query error: Unspecified error
>This error is new; I am able to query and get results from the tables in
>query analyzer and I am able to view the tables through Enterprise Manager
>when I link to these databases from another computer. I restarted SQL serv
er
>without any luck. Do you think it needs to be reinstalled?

error opening table in Enterprise MGR

I am getting an error message when I try to open (to view the rows of) any
table in any of the databases on a SQL 7 server from the server where the
databases actually reside- it says:
"An unexpected error happened during this operation. [Query] - Query
Designer encountered a query error: Unspecified error
This error is new; I am able to query and get results from the tables in
query analyzer and I am able to view the tables through Enterprise Manager
when I link to these databases from another computer. I restarted SQL server
without any luck. Do you think it needs to be reinstalled?Check the following article which addresses the issue:
FIX: Enterprise Manager Returns Unexpected Error on Table or
View
http://support.microsoft.com/?id=273472
-Sue
On Wed, 26 Jan 2005 07:47:03 -0800, "PatW"
<PatW@.discussions.microsoft.com> wrote:
>I am getting an error message when I try to open (to view the rows of) any
>table in any of the databases on a SQL 7 server from the server where the
>databases actually reside- it says:
>"An unexpected error happened during this operation. [Query] - Query
>Designer encountered a query error: Unspecified error
>This error is new; I am able to query and get results from the tables in
>query analyzer and I am able to view the tables through Enterprise Manager
>when I link to these databases from another computer. I restarted SQL server
>without any luck. Do you think it needs to be reinstalled?

Error opening datafile: The filename, directory name, or volume labe syntax inco

I receive this error message when I try and run my DTS package:

"Error opening datafile: The filename, directory name, or volume labe syntax is incorrect."

I set the file name property of the Text File (Source) to a valid file, but when I run the package and it returns the above error message, it sets the file name property to <not displayable>.

Does anyone have any experience with such a problem? If so please help!!! ThanksRunning scheduled or manual?|||it's run manually triggerred from an ASP page.|||bump|||Well...

It's running under the context of the login that calls it...but how are you executing from an asp page?

From a job or sproc?

Usually when it runs under the contect of the server the file paths and names have to exists ON the server, not the client.

Is that your understanding?|||It throws the afforementioned error when I call it from ASP or from the Enterprise Manager.

I'm executing it from asp like:
Set oPkg = Server.CreateObject("DTS.Package")
oPkg.Execute

But the fact that it throws the error from EM on the server is most alarming. I just returned from vacation and I have no idea what could be causing this.

The file names do exist on the local server, but when the package is run it sets the file name property to "<not displayable>"sql

Error opening datafile: filename, directory, volume syntax incorrect

I receive this error message when I try and run my DTS
package:

"Error opening datafile: The filename, directory name, or
volume label syntax is incorrect."

I set the file name property of the Text File (Source) to
a valid file, but when I run the package and it returns
the above error message, it sets the file name property
to <not displayable>.

Does anyone have any experience with such a problem? If
so please help!!! ThanksIt throws the afforementioned error when I call it from ASP or from the Enterprise Manager.

I'm executing it from asp like:
Set oPkg = Server.CreateObject("DTS.Package")
oPkg.Execute

But the fact that it throws the error from EM on the server is most alarming. I just returned from vacation and I have no idea what could be causing this.

The file names do exist on the local server, but when the package is run it sets the file name property to "<not displayable>"

Error on VB Sample which is delivered by installation.

Hi,

after i try to build the web application "Web Development - Data Entry Form" i get the following error message. I already change the variable username to system which is defined in Machine.Config.

The Error messega is like following:
SQL Server does not exist or access denied.
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.Data.SqlClient.SqlException: SQL Server does not exist or access denied.

Thanks,The username you see in machine.config is most likely not the username you want to provide in the connection string in your application. You need to provide a valid username and password for your SQL server. If you did not install the db server yourself, you should be able to get valid login info from the person who installed it.

If the db server is local, you might be able to get away with the following for your connection string: "server=localhost;TrustedConnection=true;database=YOUR_DB"

error on report server

when I try to run the report from VS.NET (SQL Server 2005 Business
Intelligence Development Studio). I got the following message:
======================================================================= TITLE: Microsoft Report Designer
--
A connection could not be made to the report server
http://localhost/ReportServer2005.
--
ADDITIONAL INFORMATION:
Client found response content type of 'text/html; charset=utf-8', but
expected 'text/xml'.
The request failed with the error message:
--
<html>
<head>
<title>
SQL Server Reporting Services
</title><meta name="Generator" content="Microsoft SQL Server Reporting
Services 9.00.1399.00" />
<meta name="HTTP Status" content="500" />
<meta name="ProductLocaleID" content="9" />
<meta name="CountryLocaleID" content="1033" />
<meta name="StackTrace" content=" at
Microsoft.ReportingServices.Diagnostics.RSConfiguration.Load()
at
Microsoft.ReportingServices.Diagnostics.RSConfiguration.Construct(String
configFileName)
at Microsoft.ReportingServices.Diagnostics.RSConfiguration..ctor(String
configFileName, String location)
at
Microsoft.ReportingServices.Diagnostics.RSConfigurationManager..ctor(String
configFileName, String configLocation)
at Microsoft.ReportingServices.Library.Global.get_ConfigurationManager()
at Microsoft.ReportingServices.WebServer.Global.StartApp()
at
Microsoft.ReportingServices.WebServer.Global.Application_BeginRequest(Object
sender, EventArgs e)" />
<style>
BODY {FONT-FAMILY:Verdana; FONT-WEIGHT:normal; FONT-SIZE: 8pt;
COLOR:black}
H1 {FONT-FAMILY:Verdana; FONT-WEIGHT:700; FONT-SIZE:15pt}
LI {FONT-FAMILY:Verdana; FONT-WEIGHT:normal; FONT-SIZE:8pt;
DISPLAY:inline}
.ProductInfo {FONT-FAMILY:Verdana; FONT-WEIGHT:bold; FONT-SIZE: 8pt;
COLOR:gray}
A:link {FONT-SIZE: 8pt; FONT-FAMILY:Verdana; COLOR:#3366CC;
TEXT-DECORATION:none}
A:hover {FONT-SIZE: 8pt; FONT-FAMILY:Verdana; COLOR:#FF3300;
TEXT-DECORATION:underline}
A:visited {FONT-SIZE: 8pt; FONT-FAMILY:Verdana; COLOR:#3366CC;
TEXT-DECORATION:none}
A:visited:hover {FONT-SIZE: 8pt; FONT-FAMILY:Verdana; color:#FF3300;
TEXT-DECORATION:underline}
</style>
</head><body bgcolor="white">
<h1>
Reporting Services Error<hr width="100%" size="1" color="silver" />
</h1><ul>
<li>The report server has encountered a configuration error. See the
report server log files for more information. (rsServerConfigurationError)
</li><ul>
<li>Access to the path 'C:\Program Files\Microsoft SQL
Server\MSSQL.3\Reporting Services\ReportServer\RSReportServer.config' is
denied.</li>
</ul>
</ul><hr width="100%" size="1" color="silver" /><span
class="ProductInfo">SQL Server Reporting Services</span>
</body>
</html>
--. (Microsoft.ReportingServices.Designer)
--
BUTTONS:
OK
--
=======================================================================
This is the error message I got when I try to run
http:\\localhost\reportserver2005 in IE. I got same error message when I run
http:\\MachineName\reportserver2005.
======================================================================= Reporting Services Error
----
a.. The report server has encountered a configuration error. See the
report server log files for more information. (rsServerConfigurationError)
a.. Access to the path 'C:\Program Files\Microsoft SQL
Server\MSSQL.3\Reporting Services\ReportServer\RSReportServer.config' is
denied.
----
SQL Server Reporting Services
=======================================================================
Please help!
Thank you very much
Darren L.Can you access http://localhost/Reports ? This is the default setting.
It looks like some setting problem. What does the log file say?|||Hi,
I ran http://localhost/Reports2005, I got following error:
The report server is not responding. Verify that the report server is
running and can be accessed from this computer.
I am thinking the problem maybe the setup (installation). I have SQL
Server 2000 Reports Service on my machine. When I installed the SQL Server
2005 Report Service. It simply tells me that report service has been
installed. So I created a new instance Reports2005 and ReportServer2005. Is
this the reason why it is not working? And what should I do to fix it?
Thanks
Darren
"Nick" <nick_1394@.yahoo.com.cn> wrote in message
news:1137696210.625104.289820@.g49g2000cwa.googlegroups.com...
> Can you access http://localhost/Reports ? This is the default setting.
> It looks like some setting problem. What does the log file say?
>|||Not sure if I am in the right log:
ReportingServicesService!library!4!1/19/2006-10:02:52:: i INFO: Initializing
ConnectionType to '0' as specified in Configuration file.
ReportingServicesService!library!4!1/19/2006-10:02:52:: i INFO: Initializing
IsSchedulingService to 'True' as specified in Configuration file.
ReportingServicesService!library!4!1/19/2006-10:02:52:: i INFO: Initializing
IsNotificationService to 'True' as specified in Configuration file.
ReportingServicesService!library!4!1/19/2006-10:02:52:: i INFO: Initializing
IsEventService to 'True' as specified in Configuration file.
ReportingServicesService!library!4!1/19/2006-10:02:52:: i INFO: Initializing
PollingInterval to '10' second(s) as specified in Configuration file.
ReportingServicesService!library!4!1/19/2006-10:02:52:: i INFO: Initializing
WindowsServiceUseFileShareStorage to 'False' as specified in Configuration
file.
ReportingServicesService!library!4!1/19/2006-10:02:52:: i INFO: Initializing
MemoryLimit to '60' percent as specified in Configuration file.
ReportingServicesService!library!4!1/19/2006-10:02:52:: i INFO: Initializing
RecycleTime to '720' minute(s) as specified in Configuration file.
ReportingServicesService!library!4!1/19/2006-10:02:52:: i INFO: Initializing
MaximumMemoryLimit to '80' percent as specified in Configuration file.
ReportingServicesService!library!4!1/19/2006-10:02:52:: i INFO: Initializing
MaxAppDomainUnloadTime to '30' minute(s) as specified in Configuration file.
ReportingServicesService!library!4!1/19/2006-10:02:52:: i INFO: Initializing
MaxQueueThreads to '0' thread(s) as specified in Configuration file.
ReportingServicesService!library!4!1/19/2006-10:02:52:: i INFO: Initializing
IsWebServiceEnabled to 'True' as specified in Configuration file.
ReportingServicesService!configmanager!4!1/19/2006-10:02:52:: w WARN:
WebServiceAccount is not specified in the config file. Using default:
DL-DELL700M\ASPNET
ReportingServicesService!library!4!1/19/2006-10:02:52:: i INFO: Initializing
MaxActiveReqForOneUser to '20' requests(s) as specified in Configuration
file.
ReportingServicesService!library!4!1/19/2006-10:02:52:: i INFO: Initializing
MaxScheduleWait to '5' second(s) as specified in Configuration file.
ReportingServicesService!library!4!1/19/2006-10:02:52:: i INFO: Initializing
DatabaseQueryTimeout to '120' second(s) as specified in Configuration file.
ReportingServicesService!library!4!1/19/2006-10:02:52:: i INFO: Initializing
ProcessRecycleOptions to '0' as specified in Configuration file.
ReportingServicesService!library!4!1/19/2006-10:02:52:: i INFO: Initializing
RunningRequestsScavengerCycle to '60' second(s) as specified in
Configuration file.
ReportingServicesService!library!4!1/19/2006-10:02:52:: i INFO: Initializing
RunningRequestsDbCycle to '60' second(s) as specified in Configuration file.
ReportingServicesService!library!4!1/19/2006-10:02:52:: i INFO: Initializing
RunningRequestsAge to '30' second(s) as specified in Configuration file.
ReportingServicesService!library!4!1/19/2006-10:02:52:: i INFO: Initializing
CleanupCycleMinutes to '10' minute(s) as specified in Configuration file.
ReportingServicesService!library!4!1/19/2006-10:02:52:: i INFO: Initializing
DailyCleanupMinuteOfDay to default value of '120' minutes since midnight
because it was not specified in Configuration file.
ReportingServicesService!library!4!1/19/2006-10:02:52:: i INFO: Initializing
WatsonFlags to '1064' as specified in Configuration file.
ReportingServicesService!library!4!1/19/2006-10:02:52:: i INFO: Initializing
WatsonDumpOnExceptions to
'Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException,Microsoft.ReportingServices.Modeling.InternalModelingException'
as specified in Configuration file.
ReportingServicesService!library!4!1/19/2006-10:02:52:: i INFO: Initializing
WatsonDumpExcludeIfContainsExceptions to
'System.Data.SqlClient.SqlException,System.Threading.ThreadAbortException'
as specified in Configuration file.
ReportingServicesService!library!4!1/19/2006-10:02:52:: i INFO: Initializing
SecureConnectionLevel to '0' as specified in Configuration file.
ReportingServicesService!library!4!1/19/2006-10:02:52:: i INFO: Initializing
DisplayErrorLink to 'True' as specified in Configuration file.
ReportingServicesService!library!4!1/19/2006-10:02:52:: i INFO: Initializing
WebServiceUseFileShareStorage to 'False' as specified in Configuration
file.
ReportingServicesService!servicecontroller!9!1/19/2006-10:02:57:: Total
Physical memory: 1055309824
ReportingServicesService!servicecontroller!4!1/19/2006-10:02:58:: i INFO:
RPC Server started. Endpoint name ='ReportingServices$MSSQL.3'
ReportingServicesService!library!3!1/19/2006-10:21:54:: i INFO: Catalog SQL
Server Edition = Developer
ReportingServicesService!resourceutilities!3!1/19/2006-10:21:54:: i INFO:
Reporting Services starting SKU: Standard
ReportingServicesService!resourceutilities!3!1/19/2006-10:21:54:: i INFO:
Evaluation copy: 0 days left
ReportingServicesService!library!3!1/19/2006-10:21:54:: e ERROR: restricted
SKUs: Workgroup Express Developer Evaluation - actual SKU Developer
ReportingServicesService!library!3!1/19/2006-10:21:54:: e ERROR: Throwing
Microsoft.ReportingServices.Diagnostics.Utilities.OperationNotSupportedException:
The feature: "Using other editions of SQL Server for report data sources
and/or the report server database" is not supported in this edition of
Reporting Services., ;
Info:
Microsoft.ReportingServices.Diagnostics.Utilities.OperationNotSupportedException:
The feature: "Using other editions of SQL Server for report data sources
and/or the report server database" is not supported in this edition of
Reporting Services.
ReportingServicesService!library!a!1/19/2006-10:21:54:: i INFO: Catalog SQL
Server Edition = Developer
ReportingServicesService!library!a!1/19/2006-10:21:54:: e ERROR: restricted
SKUs: Workgroup Express Developer Evaluation - actual SKU Developer
ReportingServicesService!library!a!1/19/2006-10:21:54:: e ERROR: Throwing
Microsoft.ReportingServices.Diagnostics.Utilities.OperationNotSupportedException:
The feature: "Using other editions of SQL Server for report data sources
and/or the report server database" is not supported in this edition of
Reporting Services., ;
Info:
Microsoft.ReportingServices.Diagnostics.Utilities.OperationNotSupportedException:
The feature: "Using other editions of SQL Server for report data sources
and/or the report server database" is not supported in this edition of
Reporting Services.
ReportingServicesService!library!3!1/19/2006-10:21:55:: i INFO: Catalog SQL
Server Edition = Developer
ReportingServicesService!library!3!1/19/2006-10:21:55:: e ERROR: restricted
SKUs: Workgroup Express Developer Evaluation - actual SKU Developer
ReportingServicesService!library!3!1/19/2006-10:21:55:: e ERROR: Throwing
Microsoft.ReportingServices.Diagnostics.Utilities.OperationNotSupportedException:
The feature: "Using other editions of SQL Server for report data sources
and/or the report server database" is not supported in this edition of
Reporting Services., ;
Info:
Microsoft.ReportingServices.Diagnostics.Utilities.OperationNotSupportedException:
The feature: "Using other editions of SQL Server for report data sources
and/or the report server database" is not supported in this edition of
Reporting Services.
There are few error statements at the buttom. But...
Thanks
Darren L.
"Nick" <nick_1394@.yahoo.com.cn> wrote in message
news:1137696210.625104.289820@.g49g2000cwa.googlegroups.com...
> Can you access http://localhost/Reports ? This is the default setting.
> It looks like some setting problem. What does the log file say?
>

error on building up where clause statement

how can I resolve this error message coming from the line of code used to
build up a whereclause ?
error message
--
syntax error converting the varchar value ' and IDUser >= 1 ' to a column of
data type int
sproc
--
...
IF @.ClientID <> -1 BEGIN SET @.WhereClause = @.WhereClause + ' and IDuser = '
+ @.ClientID END
IF @.ClientID = -1 BEGIN SET @.WhereClause = @.WhereClause + ' and IDuser >= 1
' END
...SQL Server thinks that you want to mathematical add two numbers together
because there is a INT in the addition. To Keep sure to concat the two
strings together you have to cast the INT value to a character type like
varchar(10), so the whole expression should be:

> IF @.ClientID <> -1 BEGIN SET @.WhereClause = @.WhereClause + ' and IDuser =
> ' + CAST(@.ClientID AS VARCHAR(50)) END
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
--
"TJS" <nospam@.here.com> schrieb im Newsbeitrag
news:e9a6rJuaFHA.584@.TK2MSFTNGP15.phx.gbl...
> how can I resolve this error message coming from the line of code used to
> build up a whereclause ?
> error message
> --
> syntax error converting the varchar value ' and IDUser >= 1 ' to a column
> of data type int
> sproc
> --
> ...
> IF @.ClientID <> -1 BEGIN SET @.WhereClause = @.WhereClause + ' and IDuser =
> ' + @.ClientID END
> IF @.ClientID = -1 BEGIN SET @.WhereClause = @.WhereClause + ' and IDuser >=
> 1 ' END
> ...
>|||thanks for replying, I tried your suggestion but I still get the same error
"Jens Smeyer" <Jens@.Remove_this_For_Contacting.sqlserver2005.de> wrote in
message news:e5hlJguaFHA.3572@.TK2MSFTNGP12.phx.gbl...
> SQL Server thinks that you want to mathematical add two numbers together
> because there is a INT in the addition. To Keep sure to concat the two
> strings together you have to cast the INT value to a character type like
> varchar(10), so the whole expression should be:
>
> --
> HTH, Jens Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
> "TJS" <nospam@.here.com> schrieb im Newsbeitrag
> news:e9a6rJuaFHA.584@.TK2MSFTNGP15.phx.gbl...
>|||Can you send in he whole statements and the exact error to see where the
Parser throws the error ?
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
--
"TJS" <nospam@.here.com> schrieb im Newsbeitrag
news:OKz0PDvaFHA.2768@.tk2msftngp13.phx.gbl...
> thanks for replying, I tried your suggestion but I still get the same
> error
>
> "Jens Smeyer" <Jens@.Remove_this_For_Contacting.sqlserver2005.de> wrote
> in message news:e5hlJguaFHA.3572@.TK2MSFTNGP12.phx.gbl...
>|||Could it be that @.WhereClause is declared as integer?
Ral Moloye|||here is current version, the purpose of the sproc is to return a list if
matching record id's
based on filter parameters provided.
========================================
============================
Alter Procedure "ListID"
(
@.admin nvarchar(10),
@.YearID int,
@.ClientID int,
@.ProjectID int
)
As
DECLARE @.List varchar(100)
DECLARE @.WhereClause nvarchar (1000)
DECLARE @.CastString1 varchar (50)
DECLARE @.CastString2 varchar (50)
SET @.WhereClause=''
SET @.CastString1 = ' and IDuser >= ' + CAST(@.ClientID AS VARCHAR(50))
SET @.CastString2 = ' and IDuser = ' + CAST(@.ClientID AS VARCHAR(50))
-- Define the selection criteria for client depending on whether or not
user is an admin
-- ----
---
IF @.admin = 'true' and @.ClientID = -1 BEGIN SET @.WhereClause =
@.WhereClause + @.CastString1 END
IF @.admin = 'true' and @.ClientID <> -1 BEGIN SET @.WhereClause =
@.WhereClause + @.CastString2 END
IF @.admin = 'false' BEGIN SET @.WhereClause = @.WhereClause +
@.CastString2 END
-- Define the selection criteria for selections of project and year
-- ----
---
IF @.ProjectID <> -1 BEGIN SET @.WhereClause = @.WhereClause + ' and IDProject
= ' + @.ProjectID END
IF @.YearID <> -1 BEGIN SET @.WhereClause = @.WhereClause + ' and
year(issueDate) = ' + @.YearID END
-- retrieve selection
-- ----
---
SELECT @.List = COALESCE(@.List + ', ', '') + CAST(InvoiceID AS varchar(5))
FROM invoices, Projects
WHERE Projects.ProjectID = Invoices.IDProject + @.WhereClause
-- return results
-- ----
---
SELECT @.List|||Everywhere where a INt takes place (doesntmatter if you declared it in your
procedure or you get it from the database) and you want to add it to the
string, SQL Server will try to do a methematical addition to the strings
which wont work, so you will have to replace that in your whole code (e.g.
For YearID, projectId ...)
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
--
"TJS" <nospam@.here.com> schrieb im Newsbeitrag
news:uVOaKl4aFHA.3840@.tk2msftngp13.phx.gbl...
> here is current version, the purpose of the sproc is to return a list if
> matching record id's
> based on filter parameters provided.
> ========================================
============================
> Alter Procedure "ListID"
> (
> @.admin nvarchar(10),
> @.YearID int,
> @.ClientID int,
> @.ProjectID int
> )
> As
> DECLARE @.List varchar(100)
> DECLARE @.WhereClause nvarchar (1000)
> DECLARE @.CastString1 varchar (50)
> DECLARE @.CastString2 varchar (50)
> SET @.WhereClause=''
> SET @.CastString1 = ' and IDuser >= ' + CAST(@.ClientID AS VARCHAR(50))
> SET @.CastString2 = ' and IDuser = ' + CAST(@.ClientID AS VARCHAR(50))
> -- Define the selection criteria for client depending on whether or not
> user is an admin
> -- ----
---
> IF @.admin = 'true' and @.ClientID = -1 BEGIN SET @.WhereClause =
> @.WhereClause + @.CastString1 END
> IF @.admin = 'true' and @.ClientID <> -1 BEGIN SET @.WhereClause =
> @.WhereClause + @.CastString2 END
> IF @.admin = 'false' BEGIN SET @.WhereClause = @.WhereClause +
> @.CastString2 END
> -- Define the selection criteria for selections of project and year
> -- ----
---
> IF @.ProjectID <> -1 BEGIN SET @.WhereClause = @.WhereClause + ' and
> IDProject = ' + @.ProjectID END
> IF @.YearID <> -1 BEGIN SET @.WhereClause = @.WhereClause + ' and
> year(issueDate) = ' + @.YearID END
> -- retrieve selection
> -- ----
---
> SELECT @.List = COALESCE(@.List + ', ', '') + CAST(InvoiceID AS varchar(5))
> FROM invoices, Projects
> WHERE Projects.ProjectID = Invoices.IDProject + @.WhereClause
> -- return results
> -- ----
---
> SELECT @.List
>

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.|||

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.|||

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.|||

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.|||

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.|||

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.|||

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.|||

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.