Case sensitivity of SQL selects

Hi all
Can anybody tell me how to give a case sensitive select on a non case sensitive instance of sql server .Is there any setting to be set up ( Which needs to be done programtically not through the interface )
Thanks
RoshanAssuming SQL 2000, you can specify a case-sensitive collation for a
case-sensitive query. For example:
USE Northwind
SELECT *
FROM Customers
WHERE CustomerID = 'alfki' COLLATE SQL_Latin1_General_CP850_BIN
SELECT *
FROM Customers
WHERE CustomerID = 'ALFKI' COLLATE SQL_Latin1_General_CP850_BIN
You can also add the case-insensitive condition so that indexes can be used
efficiently.
SELECT *
FROM Customers
WHERE CustomerID = 'alfki' COLLATE SQL_Latin1_General_CP850_BIN
AND CustomerID = 'alfki'
SELECT *
FROM Customers
WHERE CustomerID = 'ALFKI' COLLATE SQL_Latin1_General_CP850_BIN
AND CustomerID = 'ALFKI'
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Roshan Jayalath" <anonymous@.discussions.microsoft.com> wrote in message
news:648CCD5F-2615-4730-B735-3AED0EEEB4CB@.microsoft.com...
> Hi all,
> Can anybody tell me how to give a case sensitive select on a non case
sensitive instance of sql server .Is there any setting to be set up ( Which
needs to be done programtically not through the interface ) ?
> Thanks
> Roshan|||In addition Dan's post
This should work on SQL 7 too
create table ABCD
(
courceid smallint not null,
description varchar(20) null
)
insert into ABCD(courceid,description)values (1,'DFh2AcZ')
insert into ABCD(courceid,description)values (2,'dHZ3')
)
SELECT description FROM ABCD where charindex(cast('H' as
varbinary(20)),cast(description as varbinary(20)))> 0
"Dan Guzman" <danguzman@.nospam-earthlink.net> wrote in message
news:u2gDRbBKEHA.3596@.tk2msftngp13.phx.gbl...
> Assuming SQL 2000, you can specify a case-sensitive collation for a
> case-sensitive query. For example:
> USE Northwind
> SELECT *
> FROM Customers
> WHERE CustomerID = 'alfki' COLLATE SQL_Latin1_General_CP850_BIN
> SELECT *
> FROM Customers
> WHERE CustomerID = 'ALFKI' COLLATE SQL_Latin1_General_CP850_BIN
> You can also add the case-insensitive condition so that indexes can be
used
> efficiently.
> SELECT *
> FROM Customers
> WHERE CustomerID = 'alfki' COLLATE SQL_Latin1_General_CP850_BIN
> AND CustomerID = 'alfki'
> SELECT *
> FROM Customers
> WHERE CustomerID = 'ALFKI' COLLATE SQL_Latin1_General_CP850_BIN
> AND CustomerID = 'ALFKI'
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Roshan Jayalath" <anonymous@.discussions.microsoft.com> wrote in message
> news:648CCD5F-2615-4730-B735-3AED0EEEB4CB@.microsoft.com...
> > Hi all,
> >
> > Can anybody tell me how to give a case sensitive select on a non case
> sensitive instance of sql server .Is there any setting to be set up (
Which
> needs to be done programtically not through the interface ) ?
> >
> > Thanks
> > Roshan
>sql

Case sensitivity of SQL selects

Hi all,
Can anybody tell me how to give a case sensitive select on a non case sensitive instance of sql server .Is there any setting to be set up ( Which needs to be done programtically not through the interface ) ?
Thanks
Roshan
Assuming SQL 2000, you can specify a case-sensitive collation for a
case-sensitive query. For example:
USE Northwind
SELECT *
FROM Customers
WHERE CustomerID = 'alfki' COLLATE SQL_Latin1_General_CP850_BIN
SELECT *
FROM Customers
WHERE CustomerID = 'ALFKI' COLLATE SQL_Latin1_General_CP850_BIN
You can also add the case-insensitive condition so that indexes can be used
efficiently.
SELECT *
FROM Customers
WHERE CustomerID = 'alfki' COLLATE SQL_Latin1_General_CP850_BIN
AND CustomerID = 'alfki'
SELECT *
FROM Customers
WHERE CustomerID = 'ALFKI' COLLATE SQL_Latin1_General_CP850_BIN
AND CustomerID = 'ALFKI'
Hope this helps.
Dan Guzman
SQL Server MVP
"Roshan Jayalath" <anonymous@.discussions.microsoft.com> wrote in message
news:648CCD5F-2615-4730-B735-3AED0EEEB4CB@.microsoft.com...
> Hi all,
> Can anybody tell me how to give a case sensitive select on a non case
sensitive instance of sql server .Is there any setting to be set up ( Which
needs to be done programtically not through the interface ) ?
> Thanks
> Roshan
|||In addition Dan's post
This should work on SQL 7 too
create table ABCD
(
courceid smallint not null,
description varchar(20) null
)
insert into ABCD(courceid,description)values (1,'DFh2AcZ')
insert into ABCD(courceid,description)values (2,'dHZ3')
)
SELECT description FROM ABCD where charindex(cast('H' as
varbinary(20)),cast(description as varbinary(20)))> 0
"Dan Guzman" <danguzman@.nospam-earthlink.net> wrote in message
news:u2gDRbBKEHA.3596@.tk2msftngp13.phx.gbl...
> Assuming SQL 2000, you can specify a case-sensitive collation for a
> case-sensitive query. For example:
> USE Northwind
> SELECT *
> FROM Customers
> WHERE CustomerID = 'alfki' COLLATE SQL_Latin1_General_CP850_BIN
> SELECT *
> FROM Customers
> WHERE CustomerID = 'ALFKI' COLLATE SQL_Latin1_General_CP850_BIN
> You can also add the case-insensitive condition so that indexes can be
used
> efficiently.
> SELECT *
> FROM Customers
> WHERE CustomerID = 'alfki' COLLATE SQL_Latin1_General_CP850_BIN
> AND CustomerID = 'alfki'
> SELECT *
> FROM Customers
> WHERE CustomerID = 'ALFKI' COLLATE SQL_Latin1_General_CP850_BIN
> AND CustomerID = 'ALFKI'
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Roshan Jayalath" <anonymous@.discussions.microsoft.com> wrote in message
> news:648CCD5F-2615-4730-B735-3AED0EEEB4CB@.microsoft.com...
> sensitive instance of sql server .Is there any setting to be set up (
Which
> needs to be done programtically not through the interface ) ?
>

Case sensitivity of SQL selects

Hi all,
Can anybody tell me how to give a case sensitive select on a non case sensit
ive instance of sql server .Is there any setting to be set up ( Which needs
to be done programtically not through the interface ) ?
Thanks
RoshanAssuming SQL 2000, you can specify a case-sensitive collation for a
case-sensitive query. For example:
USE Northwind
SELECT *
FROM Customers
WHERE CustomerID = 'alfki' COLLATE SQL_Latin1_General_CP850_BIN
SELECT *
FROM Customers
WHERE CustomerID = 'ALFKI' COLLATE SQL_Latin1_General_CP850_BIN
You can also add the case-insensitive condition so that indexes can be used
efficiently.
SELECT *
FROM Customers
WHERE CustomerID = 'alfki' COLLATE SQL_Latin1_General_CP850_BIN
AND CustomerID = 'alfki'
SELECT *
FROM Customers
WHERE CustomerID = 'ALFKI' COLLATE SQL_Latin1_General_CP850_BIN
AND CustomerID = 'ALFKI'
Hope this helps.
Dan Guzman
SQL Server MVP
"Roshan Jayalath" <anonymous@.discussions.microsoft.com> wrote in message
news:648CCD5F-2615-4730-B735-3AED0EEEB4CB@.microsoft.com...
> Hi all,
> Can anybody tell me how to give a case sensitive select on a non case
sensitive instance of sql server .Is there any setting to be set up ( Which
needs to be done programtically not through the interface ) ?
> Thanks
> Roshan|||In addition Dan's post
This should work on SQL 7 too
create table ABCD
(
courceid smallint not null,
description varchar(20) null
)
insert into ABCD(courceid,description)values (1,'DFh2AcZ')
insert into ABCD(courceid,description)values (2,'dHZ3')
)
SELECT description FROM ABCD where charindex(cast('H' as
varbinary(20)),cast(description as varbinary(20)))> 0
"Dan Guzman" <danguzman@.nospam-earthlink.net> wrote in message
news:u2gDRbBKEHA.3596@.tk2msftngp13.phx.gbl...
> Assuming SQL 2000, you can specify a case-sensitive collation for a
> case-sensitive query. For example:
> USE Northwind
> SELECT *
> FROM Customers
> WHERE CustomerID = 'alfki' COLLATE SQL_Latin1_General_CP850_BIN
> SELECT *
> FROM Customers
> WHERE CustomerID = 'ALFKI' COLLATE SQL_Latin1_General_CP850_BIN
> You can also add the case-insensitive condition so that indexes can be
used
> efficiently.
> SELECT *
> FROM Customers
> WHERE CustomerID = 'alfki' COLLATE SQL_Latin1_General_CP850_BIN
> AND CustomerID = 'alfki'
> SELECT *
> FROM Customers
> WHERE CustomerID = 'ALFKI' COLLATE SQL_Latin1_General_CP850_BIN
> AND CustomerID = 'ALFKI'
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Roshan Jayalath" <anonymous@.discussions.microsoft.com> wrote in message
> news:648CCD5F-2615-4730-B735-3AED0EEEB4CB@.microsoft.com...
> sensitive instance of sql server .Is there any setting to be set up (
Which
> needs to be done programtically not through the interface ) ?
>

case sensitive server - problems running scripts

I have just been given a new SQL Server 2000 box to look after in production. I just tried to run a standard t-sql script I use for setting up backup jobs and so on. However, it failed with a long list of errors - quite a surprise at first since I have run the same script on many other servers wihtout a hitch. On close examination, the problem appears to be that the new serer is setup with a server default collation... Latin1_General_BIN (I think a binary based collation makes this a case sensitive server).

This is quite an urgenet one since I have to get this wrapped up today. I don't think I can change the server's default collation without a lot of red-tape. Is there a quick way to run my scripts in a 'case insenstive' context within Query Analyzer? If so, how?

Thanks in advance,

CliveWe have that problem all of the time with the PeopleSoft servers. They can only run with binary sort orders.

If you find a way to work around the case sensitivity, please let me know!

-PatP|||Ok, well thanks anyway. It seems a bit over the top for a server to be set to case senstive by default. Even the master database is case sensitive as a result. I can't see why the s/w vendor couldn't have left the default server collation alone and just been a bit more selective about what tables/columns actually needed a _BIN collation. Laziness I suppose.

Clive|||Binary sort order os a bit faster than case sensitive, as it bypasses all of the checks for 'A' = 'a'. That aside, you should probably go over the script and change the identifiers (table names, column names) to be the proper case (fortunately this is all lowercase for system tables), and change all of your variables to be the same case throughout. The variables can be doe with find/replace very easily. After that, you would have a new script that would work on Latin1_General_CI_AS, _BIN, and _CS_AS servers.

Since i have a couple of case sensitive servers around, I have had to write all of my own scripts to be able to handle case sensitivity. Even the ones that "should" only run on the case insensitive ones. It is a good habit to get into.|||All of our main production servers are Latin1_General_BIN_437 which is actually what yours probably is. This was recommended back in the old days when it was based on 6.5. Since they reworked the architecture, It doesn't really make any difference on speed. Since it's not the industry standard to use this, it's just a big pain. Anyway, I've learned to use all upper-case for my commands and lower-case for my objects. We have a program at work that will automagically convert all your code for you. I'll see if I can "share" it with you. Saves soooooooo much time.

Case in Where Clause

Can you put a Case statement in a Where clause?
I have the following Cursor I am setting up that is giving me the error:
Server: Msg 170, Level 15, State 1, Line 26
Line 26: Incorrect syntax near '>'.
Declare @.SearchCursor Cursor
Set @.SearchCursor = Cursor for Select
CommandText,WhereClause,SearchID,UserID
from CandidateSearches where SearchAgent=1 and SearchAgentActive=1 and
(CASE WHEN NotifyFrequency = 'D' THEN
(DATEDIFF(DAY,SearchAgentLastRun,GetDate
()) > 0)
WHEN NotifyFrequency = 'W' THEN
(DATEDIFF(DAY,SearchAgentLastRun,GetDate
()) >= 7)
WHEN NotifyFrequency = 'M' THEN
(DATEDIFF(DAY,SEarchAgentLastRun,GetDate
()) >= 30) END)
Line 26 is the line the Case Statement is on.
What is the problem with this line?
Thanks,
TomHi Tom
The most important thing to keep in mind is that there is no case STATEMENT
in Transact-SQL. There is a case EXPRESSION, which can be used anywhere you
use an expression. So, you can use a case EXPRESSION in a WHERE, in place of
a value.
Without any more details like the DDL, or a description of what you're
trying to accomplish, my guess is that you want to compare
DATEDIFF(DAY,SearchAgentLastRun,GetDate(
)) to one of several different
values, depending on the value of NotifyFrequency. If that is a correct
understanding, you might try something like this in your WHERE clause:
where SearchAgent=1 and SearchAgentActive=1 and
DATEDIFF(DAY,SearchAgentLastRun,GetDate(
)) >= CASE NotifyFrequency
WHEN 'D' THEN 0
WHEN 'W' THEN 7
WHEN 'M' THEN 30
END
Also make sure to consider the case where NotifyFrequency is not one of (D,
W, M)
--
HTH
Kalen Delaney, SQL Server MVP
www.solidqualitylearning.com
"tshad" <tscheiderich@.ftsolutions.com> wrote in message
news:eeyXs5cMGHA.3960@.TK2MSFTNGP09.phx.gbl...
> Can you put a Case statement in a Where clause?
> I have the following Cursor I am setting up that is giving me the error:
> Server: Msg 170, Level 15, State 1, Line 26
> Line 26: Incorrect syntax near '>'.
> Declare @.SearchCursor Cursor
> Set @.SearchCursor = Cursor for Select
> CommandText,WhereClause,SearchID,UserID
> from CandidateSearches where SearchAgent=1 and SearchAgentActive=1 and
> (CASE WHEN NotifyFrequency = 'D' THEN
> (DATEDIFF(DAY,SearchAgentLastRun,GetDate
()) > 0)
> WHEN NotifyFrequency = 'W' THEN
> (DATEDIFF(DAY,SearchAgentLastRun,GetDate
()) >= 7)
> WHEN NotifyFrequency = 'M' THEN
> (DATEDIFF(DAY,SEarchAgentLastRun,GetDate
()) >= 30) END)
> Line 26 is the line the Case Statement is on.
> What is the problem with this line?
> Thanks,
> Tom
>|||"Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
news:OQDXBGdMGHA.500@.TK2MSFTNGP15.phx.gbl...
> Hi Tom
> The most important thing to keep in mind is that there is no case
> STATEMENT in Transact-SQL. There is a case EXPRESSION, which can be used
> anywhere you use an expression. So, you can use a case EXPRESSION in a
> WHERE, in place of a value.
> Without any more details like the DDL, or a description of what you're
> trying to accomplish, my guess is that you want to compare
> DATEDIFF(DAY,SearchAgentLastRun,GetDate(
)) to one of several different
> values, depending on the value of NotifyFrequency. If that is a correct
> understanding, you might try something like this in your WHERE clause:
Exactly, but how would I do the instance where the case of 'D' is > 0 and
not >= 0?
Thanks,
Tom

> where SearchAgent=1 and SearchAgentActive=1 and
> DATEDIFF(DAY,SearchAgentLastRun,GetDate(
)) >= CASE NotifyFrequency
> WHEN 'D' THEN 0
> WHEN 'W' THEN 7
> WHEN 'M' THEN 30
> END
> Also make sure to consider the case where NotifyFrequency is not one of
> (D, W, M)
> --
> HTH
> Kalen Delaney, SQL Server MVP
> www.solidqualitylearning.com
>
> "tshad" <tscheiderich@.ftsolutions.com> wrote in message
> news:eeyXs5cMGHA.3960@.TK2MSFTNGP09.phx.gbl...
>
>|||I think what you are trying to do is this
Declare @.SearchCursor Cursor
Set @.SearchCursor = Cursor for Select
CommandText,WhereClause,SearchID,UserID
from CandidateSearches where SearchAgent=1 and
SearchAgentActive=1 and
((NotifyFrequency = 'D'
and DATEDIFF(DAY,SearchAgentLastRun,GetDate(
)) > 0) OR
(NotifyFrequency = 'W'
and DATEDIFF(DAY,SearchAgentLastRun,GetDate(
)) >= 7) OR
(NotifyFrequency = 'M'
and DATEDIFF(DAY,SearchAgentLastRun,GetDate(
)) >= 30))|||<markc600@.hotmail.com> wrote in message
news:1140022428.091421.209720@.g14g2000cwa.googlegroups.com...
>I think what you are trying to do is this
> Declare @.SearchCursor Cursor
> Set @.SearchCursor = Cursor for Select
> CommandText,WhereClause,SearchID,UserID
> from CandidateSearches where SearchAgent=1 and
> SearchAgentActive=1 and
> ((NotifyFrequency = 'D'
> and DATEDIFF(DAY,SearchAgentLastRun,GetDate(
)) > 0) OR
> (NotifyFrequency = 'W'
> and DATEDIFF(DAY,SearchAgentLastRun,GetDate(
)) >= 7) OR
> (NotifyFrequency = 'M'
> and DATEDIFF(DAY,SearchAgentLastRun,GetDate(
)) >= 30))
That was exactly what I ended up doing. I was just curious as to how to it
(if you can do it) using the Case statement.
Thanks,
Tom|||>> Declare @.SearchCursor Cursor
>That was exactly what I ended up doing. I was just curious as to how to it
>(if you can do it) using the Case statement.
You can do it using CASE, but it doesn't let you do anything that AND,
OR and () don't already let you do. Since it resolves to a values,
you have to use it to set a value that indicates success or failure,
then test that in a comparison.
SELECT CommandText, WhereClause, SearchID, UserID
FROM CandidateSearches
WHERE SearchAgent=1
AND SearchAgentActive=1
AND CASE
WHEN NotifyFrequency = 'D'
AND DATEDIFF(DAY,SearchAgentLastRun,GetDate(
)) > 0
THEN 1
WHEN NotifyFrequency = 'W'
AND DATEDIFF(DAY,SearchAgentLastRun,GetDate(
)) >= 7
THEN 1
WHEN NotifyFrequency = 'M'
AND DATEDIFF(DAY,SearchAgentLastRun,GetDate(
)) >= 30
THEN 1
ELSE 0
END = 1
Roy|||"Roy Harvey" <roy_harvey@.snet.net> wrote in message
news:31l7v1dnjf97n234q7ih23mnbq4rtti9u1@.
4ax.com...
> You can do it using CASE, but it doesn't let you do anything that AND,
> OR and () don't already let you do. Since it resolves to a values,
> you have to use it to set a value that indicates success or failure,
> then test that in a comparison.
> SELECT CommandText, WhereClause, SearchID, UserID
> FROM CandidateSearches
> WHERE SearchAgent=1
> AND SearchAgentActive=1
> AND CASE
> WHEN NotifyFrequency = 'D'
> AND DATEDIFF(DAY,SearchAgentLastRun,GetDate(
)) > 0
> THEN 1
> WHEN NotifyFrequency = 'W'
> AND DATEDIFF(DAY,SearchAgentLastRun,GetDate(
)) >= 7
> THEN 1
> WHEN NotifyFrequency = 'M'
> AND DATEDIFF(DAY,SearchAgentLastRun,GetDate(
)) >= 30
> THEN 1
> ELSE 0
> END = 1
>
I was as to what this did at first, but then I realized what it was
doing.
In the "OR" example, I would only get a record if one of the 3 tests (as
well as the SearchAgent and SearchAgentActive) were matched.
In your example, you are testing if the Case statement was "1". It was
clear when I put parens around the case statement. I thought at first you
were setting "End=1". But when I put the parans in, it made sense:
... AND (CASE
WHEN NotifyFrequency = 'D'
AND DATEDIFF(DAY,SearchAgentLastRun,GetDate(
)) > 0
THEN 1
WHEN NotifyFrequency = 'W'
AND DATEDIFF(DAY,SearchAgentLastRun,GetDate(
)) >= 7
THEN 1
WHEN NotifyFrequency = 'M'
AND DATEDIFF(DAY,SearchAgentLastRun,GetDate(
)) >= 30
THEN 1
ELSE 0
END) = 1
I think that is what is happening.
But as you said the OR does the same thing and is a little more clear and
you don't have to do the extra step of setting it to 0 or 1.
Thanks,
Tom
> Roy

cascading parameter help - solution

I a report that will have two parameters (Year and Account name), I'm having trouble setting up the second parameter to be filtered based on the value of the first parameter.

here is the second parameter with a value hard coded.(see bold text) this works fine when I run the report.

WITH MEMBER [Measures].[ParameterCaption] AS '[CUSTOMER JOB].[ACCOUNT NAME].CURRENTMEMBER.MEMBER_CAPTION' MEMBER [Measures].[ParameterValue] AS '[CUSTOMER JOB].[ACCOUNT NAME].CURRENTMEMBER.UNIQUENAME' MEMBER [Measures].[ParameterLevel] AS '[CUSTOMER JOB].[ACCOUNT NAME].CURRENTMEMBER.LEVEL.ORDINAL' SELECT {[Measures].[ParameterCaption], [Measures].[ParameterValue], [Measures].[ParameterLevel]} ON COLUMNS ,FILTER([CUSTOMER JOB].[ACCOUNT NAME].ALLMEMBERS,([Job Complete Date].[Year].&[2006],[Measures].[Billed Sales Amount])) ON ROWS FROM [DW PREP ARCHIVE]

When I try the following code where I have added in the equal sign and double quotes I get an error message (see below)

= "WITH MEMBER [Measures].[ParameterCaption] AS '[CUSTOMER JOB].[ACCOUNT NAME].CURRENTMEMBER.MEMBER_CAPTION' MEMBER [Measures].[ParameterValue] AS '[CUSTOMER JOB].[ACCOUNT NAME].CURRENTMEMBER.UNIQUENAME' MEMBER [Measures].[ParameterLevel] AS '[CUSTOMER JOB].[ACCOUNT NAME].CURRENTMEMBER.LEVEL.ORDINAL' SELECT {[Measures].[ParameterCaption], [Measures].[ParameterValue], [Measures].[ParameterLevel]} ON COLUMNS ,FILTER([CUSTOMER JOB].[ACCOUNT NAME].ALLMEMBERS,(" & Parameter!JobCompleteDateYear.value & ",[Measures].[Billed Sales Amount])) ON ROWS FROM [DW PREP ARCHIVE]"

error message

TITLE: Microsoft Visual Studio

The query cannot be retrieved from the query builder.
Check the query for syntax errors.
Reporting Services will continue to use the most recent valid query.

ADDITIONAL INFORMATION:

Query preparation failed. (Microsoft.AnalysisServices.Controls)

Query (1, 1) Parser: The syntax for '=' is incorrect. (msmgdsrv)

BUTTONS:

OK

Any suggestions ?

thanks

I found my solution. I needed to use the Strtomember function and inserted the parameter name as @.parametername

here is the final code

before

WITH MEMBER [Measures].[ParameterCaption] AS '[CUSTOMER JOB].[ACCOUNT NAME].CURRENTMEMBER.MEMBER_CAPTION' MEMBER [Measures].[ParameterValue] AS '[CUSTOMER JOB].[ACCOUNT NAME].CURRENTMEMBER.UNIQUENAME' MEMBER [Measures].[ParameterLevel] AS '[CUSTOMER JOB].[ACCOUNT NAME].CURRENTMEMBER.LEVEL.ORDINAL' SELECT {[Measures].[ParameterCaption], [Measures].[ParameterValue], [Measures].[ParameterLevel]} ON COLUMNS ,FILTER([CUSTOMER JOB].[ACCOUNT NAME].ALLMEMBERS,([Job Complete Date].[Year].&[2006],[Measures].[Billed Sales Amount])) ON ROWS FROM [DW PREP ARCHIVE]

after

WITH MEMBER [Measures].[ParameterCaption] AS '[CUSTOMER JOB].[ACCOUNT NAME].CURRENTMEMBER.MEMBER_CAPTION' MEMBER [Measures].[ParameterValue] AS '[CUSTOMER JOB].[ACCOUNT NAME].CURRENTMEMBER.UNIQUENAME' MEMBER [Measures].[ParameterLevel] AS '[CUSTOMER JOB].[ACCOUNT NAME].CURRENTMEMBER.LEVEL.ORDINAL' SELECT {[Measures].[ParameterCaption], [Measures].[ParameterValue], [Measures].[ParameterLevel]} ON COLUMNS ,FILTER([CUSTOMER JOB].[ACCOUNT NAME].ALLMEMBERS,(Strtomember(@.JobCompleteDateYear),[Measures].[Billed Sales Amount])) ON ROWS FROM [DW PREP ARCHIVE]

cascading parameter help

I a report that will have two parameters (Year and Account name), I'm having trouble setting up the second parameter to be filtered based on the value of the first parameter.

here is the second parameter with a value hard coded.(see bold text) this works fine when I run the report.

WITH MEMBER [Measures].[ParameterCaption] AS '[CUSTOMER JOB].[ACCOUNT NAME].CURRENTMEMBER.MEMBER_CAPTION' MEMBER [Measures].[ParameterValue] AS '[CUSTOMER JOB].[ACCOUNT NAME].CURRENTMEMBER.UNIQUENAME' MEMBER [Measures].[ParameterLevel] AS '[CUSTOMER JOB].[ACCOUNT NAME].CURRENTMEMBER.LEVEL.ORDINAL' SELECT {[Measures].[ParameterCaption], [Measures].[ParameterValue], [Measures].[ParameterLevel]} ON COLUMNS ,FILTER([CUSTOMER JOB].[ACCOUNT NAME].ALLMEMBERS,([Job Complete Date].[Year].&[2006],[Measures].[Billed Sales Amount])) ON ROWS FROM [DW PREP ARCHIVE]

When I try the following code where I have added in the equal sign and double quotes I get an error message (see below)

= "WITH MEMBER [Measures].[ParameterCaption] AS '[CUSTOMER JOB].[ACCOUNT NAME].CURRENTMEMBER.MEMBER_CAPTION' MEMBER [Measures].[ParameterValue] AS '[CUSTOMER JOB].[ACCOUNT NAME].CURRENTMEMBER.UNIQUENAME' MEMBER [Measures].[ParameterLevel] AS '[CUSTOMER JOB].[ACCOUNT NAME].CURRENTMEMBER.LEVEL.ORDINAL' SELECT {[Measures].[ParameterCaption], [Measures].[ParameterValue], [Measures].[ParameterLevel]} ON COLUMNS ,FILTER([CUSTOMER JOB].[ACCOUNT NAME].ALLMEMBERS,(" & Parameter!JobCompleteDateYear.value & ",[Measures].[Billed Sales Amount])) ON ROWS FROM [DW PREP ARCHIVE]"

error message

TITLE: Microsoft Visual Studio

The query cannot be retrieved from the query builder.
Check the query for syntax errors.
Reporting Services will continue to use the most recent valid query.

ADDITIONAL INFORMATION:

Query preparation failed. (Microsoft.AnalysisServices.Controls)

Query (1, 1) Parser: The syntax for '=' is incorrect. (msmgdsrv)

BUTTONS:

OK

Any suggestions ?

thanks

I found my solution. I needed to use the Strtomember function and inserted the parameter name as @.parametername

here is the final code

before

WITH MEMBER [Measures].[ParameterCaption] AS '[CUSTOMER JOB].[ACCOUNT NAME].CURRENTMEMBER.MEMBER_CAPTION' MEMBER [Measures].[ParameterValue] AS '[CUSTOMER JOB].[ACCOUNT NAME].CURRENTMEMBER.UNIQUENAME' MEMBER [Measures].[ParameterLevel] AS '[CUSTOMER JOB].[ACCOUNT NAME].CURRENTMEMBER.LEVEL.ORDINAL' SELECT {[Measures].[ParameterCaption], [Measures].[ParameterValue], [Measures].[ParameterLevel]} ON COLUMNS ,FILTER([CUSTOMER JOB].[ACCOUNT NAME].ALLMEMBERS,([Job Complete Date].[Year].&[2006],[Measures].[Billed Sales Amount])) ON ROWS FROM [DW PREP ARCHIVE]

after

WITH MEMBER [Measures].[ParameterCaption] AS '[CUSTOMER JOB].[ACCOUNT NAME].CURRENTMEMBER.MEMBER_CAPTION' MEMBER [Measures].[ParameterValue] AS '[CUSTOMER JOB].[ACCOUNT NAME].CURRENTMEMBER.UNIQUENAME' MEMBER [Measures].[ParameterLevel] AS '[CUSTOMER JOB].[ACCOUNT NAME].CURRENTMEMBER.LEVEL.ORDINAL' SELECT {[Measures].[ParameterCaption], [Measures].[ParameterValue], [Measures].[ParameterLevel]} ON COLUMNS ,FILTER([CUSTOMER JOB].[ACCOUNT NAME].ALLMEMBERS,(Strtomember(@.JobCompleteDateYear),[Measures].[Billed Sales Amount])) ON ROWS FROM [DW PREP ARCHIVE]

Cascading Deletes

We have just upgraded from sql server 7 to sql server 2000.
The BOL talks about setting the cascading deletes
in different ways.
1. By setting the 'ON DELETE CASCADE' parameter of the
foreign key references clause in a Create Table or Alter Table
statement.
2. By Viewing the Manage Relationships Tab of the relationships
view in table design, and clicking on the 'Cascade Delete Related
Records' Checkbox.
Are these two methods the same thing?
1. talks about Contraints and 2. is refering to relaionships.
If they are not the same thing, How do I implement the cascade deletes
on existing tables, and on new tables?
Thank You for your help,
Laurence Nuttall
Programmer Analyst III
UCLA - Division of Continuing Educationthey are the same, as with ON UPDATE,
personally, i prefer to explictly delete the FK references
first, but that is just my preference so i don't delete
anything i didn't intend to, there are circumstance when
CASCADE ON UPDATE is required
>--Original Message--
>We have just upgraded from sql server 7 to sql server
2000.
>The BOL talks about setting the cascading deletes
>in different ways.
>1. By setting the 'ON DELETE CASCADE' parameter of the
> foreign key references clause in a Create Table or
Alter Table
> statement.
>2. By Viewing the Manage Relationships Tab of the
relationships
> view in table design, and clicking on the 'Cascade
Delete Related
> Records' Checkbox.
>
>Are these two methods the same thing?
>1. talks about Contraints and 2. is refering to
relaionships.
>If they are not the same thing, How do I implement the
cascade deletes
>on existing tables, and on new tables?
>Thank You for your help,
>Laurence Nuttall
>Programmer Analyst III
>UCLA - Division of Continuing Education
>
>.
>

Capitalisation

Hi Guys

Anybody tell me where of if there is a setting to set
whether or not the fields and table names need to be case
specific on SQL 2000.

I've been using SQL Server 7 where it has not been the case that the table and field names had had to be the same capitalisation-wise in running.

ie select * from tbl_example would work if the table name was Tbl_Example

I've just been trying to run the same queries on a different
server, which is running SQL 2000, and they won't execute unless the
capitalisation on the table and field names are exactly
the same.

There must be a simple setting somewhere please!You must change the collation settings. To change one or more of these settings, you must rebuild the master and user databases.

How to rebuild the master database (Rebuild Master utility)
To rebuild the master database

Shutdown Microsoft SQL Server 2000, and then run Rebuildm.exe. This is located in the Program Files\Microsoft SQL Server\80\Tools\Binn directory.

In the Rebuild Master dialog box, click Browse.

In the Browse for Folder dialog box, select the \Data folder on the SQL Server 2000 compact disc or in the shared network directory from which SQL Server 2000 was installed, and then click OK.

Click Settings. In the Collation Settings dialog box, verify or change settings used for the master database and all other databases.
Initially, the default collation settings are shown, but these may not match the collation selected during setup. You can select the same settings used during setup or select new collation settings. When done, click OK.

In the Rebuild Master dialog box, click Rebuild to start the process.
The Rebuild Master utility reinstalls the master database.

Note To continue, you may need to stop a server that is running.

Needless to say, you have to be extremely careful if you are trying to re-build your master or user databases. So I would suggest you do it only if it is abosolutely necessary. Refer to BOL for more information.

All the best

Originally posted by garethimh
Hi Guys

Anybody tell me where of if there is a setting to set
whether or not the fields and table names need to be case
specific on SQL 2000.

I've been using SQL Server 7 where it has not been the case that the table and field names had had to be the same capitalisation-wise in running.

ie select * from tbl_example would work if the table name was Tbl_Example

I've just been trying to run the same queries on a different
server, which is running SQL 2000, and they won't execute unless the
capitalisation on the table and field names are exactly
the same.

There must be a simple setting somewhere please!|||Originally posted by sbaru
You must change the collation settings. To change one or more of these settings, you must rebuild the master and user databases.

How to rebuild the master database (Rebuild Master utility)
To rebuild the master database

Shutdown Microsoft SQL Server 2000, and then run Rebuildm.exe. This is located in the Program Files\Microsoft SQL Server\80\Tools\Binn directory.

In the Rebuild Master dialog box, click Browse.

In the Browse for Folder dialog box, select the \Data folder on the SQL Server 2000 compact disc or in the shared network directory from which SQL Server 2000 was installed, and then click OK.

Click Settings. In the Collation Settings dialog box, verify or change settings used for the master database and all other databases.
Initially, the default collation settings are shown, but these may not match the collation selected during setup. You can select the same settings used during setup or select new collation settings. When done, click OK.

In the Rebuild Master dialog box, click Rebuild to start the process.
The Rebuild Master utility reinstalls the master database.

Note To continue, you may need to stop a server that is running.

Needless to say, you have to be extremely careful if you are trying to re-build your master or user databases. So I would suggest you do it only if it is abosolutely necessary. Refer to BOL for more information.

All the best

Brilliant, thanks!|||sbaru's suggetion is dead on but remember to make a backup of everything first.

Can't uninstall SQL 2005

When I try to uninstall it, I get
The setup has encountered an unexpected error while Setting Internal
Properties. The error is: Fatal error during installation.
There's an OK button which I click on it and then the uninstallation
quits. Any ideas?Hi
Check the log file in Setup Bootstrap\LOG and Setup Bootstrap\LOG\Files.
There are instructions on what the log files are in the topic "How to: View
SQL Server 2005 Setup Log File" in the Setup help files found in found in the
\Setup\help\XXXX or \Setup Bootstrap\help\XXXX directory (XXXX = language
identifier) Also check out "How to: Uninstall an Existing Instance of SQL
Server 2005 (Setup)" which will give you instruction on how to manually
remove SQL Server.
John
"Calvin.Lai@.shaw.ca" wrote:
> When I try to uninstall it, I get
> The setup has encountered an unexpected error while Setting Internal
> Properties. The error is: Fatal error during installation.
> There's an OK button which I click on it and then the uninstallation
> quits. Any ideas?
>|||This is what C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Summary.txt is saying:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Microsoft SQL Server 2005 9.00.1399.06
==============================OS Version : Microsoft Windows Server 2003 family, Enterprise
Edition Service Pack 1 (Build 3790)
Time : Tue Mar 07 08:52:10 2006
Machine : CGI-EDM02
Product : Analysis Services
Error : The setup has encountered an unexpected error while
Setting Internal Properties. The error is: Fatal error during
installation.
----
Machine : CGI-EDM02
Product : Microsoft SQL Server 2005 Analysis Services
Product Version : 9.00.1399.06
Uninstall : Failed
Log File : C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_AS.log
Last Action : SetInstanceProperty
Error String : The setup has encountered an unexpected error while
Setting Internal Properties. The error is: Fatal error during
installation.
Error Number : 29528
----
SQL Server Setup failed. For more information, review the Setup log
file in %ProgramFiles%\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Summary.txt.
Time : Tue Mar 07 08:52:38 2006
List of log files:
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_Core(Local).log
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_AS.log
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_Datastore.xml
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_.NET Framework 2.0.log
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_Core.log
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Summary.txt
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_.NET Framework 2.0
LangPack.log
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_.NET Framework Upgrade
Advisor.log
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_.NET Framework Upgrade
Advisor LangPack.log
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_.NET Framework Windows
Installer.log
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_.NET Framework Windows
Installer LangPack.log
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_Support.log
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_SCC.log
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
And also, there is no article on MS KB on how to uninstall SQL 2005
manually; there is only an article on SQL 2000.|||Hi
It appears that it is analysis services that is failing to uninstall, what
did SQLSetup0028_CGI-EDM02_AS.log say?
I was referring to the additional information in the setup help file about
removing SQL 2005 not the KB.
John
"Calvin.Lai@.shaw.ca" wrote:
> This is what C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Summary.txt is saying:
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> Microsoft SQL Server 2005 9.00.1399.06
> ==============================> OS Version : Microsoft Windows Server 2003 family, Enterprise
> Edition Service Pack 1 (Build 3790)
> Time : Tue Mar 07 08:52:10 2006
> Machine : CGI-EDM02
> Product : Analysis Services
> Error : The setup has encountered an unexpected error while
> Setting Internal Properties. The error is: Fatal error during
> installation.
> ----
> Machine : CGI-EDM02
> Product : Microsoft SQL Server 2005 Analysis Services
> Product Version : 9.00.1399.06
> Uninstall : Failed
> Log File : C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_AS.log
> Last Action : SetInstanceProperty
> Error String : The setup has encountered an unexpected error while
> Setting Internal Properties. The error is: Fatal error during
> installation.
> Error Number : 29528
> ----
>
> SQL Server Setup failed. For more information, review the Setup log
> file in %ProgramFiles%\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Summary.txt.
>
> Time : Tue Mar 07 08:52:38 2006
>
> List of log files:
> C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_Core(Local).log
> C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_AS.log
> C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_Datastore.xml
> C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_.NET Framework 2.0.log
> C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_Core.log
> C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Summary.txt
> C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_.NET Framework 2.0
> LangPack.log
> C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_.NET Framework Upgrade
> Advisor.log
> C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_.NET Framework Upgrade
> Advisor LangPack.log
> C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_.NET Framework Windows
> Installer.log
> C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_.NET Framework Windows
> Installer LangPack.log
> C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_Support.log
> C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_SCC.log
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> And also, there is no article on MS KB on how to uninstall SQL 2005
> manually; there is only an article on SQL 2000.
>|||Anyone?|||Calvin.Lai@.shaw.ca wrote:
> Anyone?
I ran into this issue, the box was rebooted durning the uninstall of
anlysis services, when it came back up - i tried to uninstall analysis
services / sql server 2005 - and could not
I then tried to uninstall the SQL 2005 backword combatiblity - it
uninstalled, and said analysis services is suspened, to continue it
will unsuspend, it did, and uninsalled ok, but i still run into issues
uninstalling anlysis services, in the log everything the uninstall
looks for is not there, but the service is still there - in the
services console.
any ideas?|||Usually the SQL 2K5 registry need to be deleted and the associated
files.
Do this at your own risk. If you are experimenting, this is the way to
go.
Do not quote me...
Those who dare will survive...

Can't uninstall SQL 2005

When I try to uninstall it, I get
The setup has encountered an unexpected error while Setting Internal
Properties. The error is: Fatal error during installation.
There's an OK button which I click on it and then the uninstallation
quits. Any ideas?Hi
Check the log file in Setup Bootstrap\LOG and Setup Bootstrap\LOG\Files.
There are instructions on what the log files are in the topic "How to: View
SQL Server 2005 Setup Log File" in the Setup help files found in found in th
e
\Setup\help\XXXX or \Setup Bootstrap\help\XXXX directory (XXXX = language
identifier) Also check out "How to: Uninstall an Existing Instance of SQL
Server 2005 (Setup)" which will give you instruction on how to manually
remove SQL Server.
John
"Calvin.Lai@.shaw.ca" wrote:

> When I try to uninstall it, I get
> The setup has encountered an unexpected error while Setting Internal
> Properties. The error is: Fatal error during installation.
> There's an OK button which I click on it and then the uninstallation
> quits. Any ideas?
>|||This is what C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Summary.txt is saying:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^^^^^^^^
Microsoft SQL Server 2005 9.00.1399.06
==============================
OS Version : Microsoft Windows Server 2003 family, Enterprise
Edition Service Pack 1 (Build 3790)
Time : Tue Mar 07 08:52:10 2006
Machine : CGI-EDM02
Product : Analysis Services
Error : The setup has encountered an unexpected error while
Setting Internal Properties. The error is: Fatal error during
installation.
----
--
Machine : CGI-EDM02
Product : Microsoft SQL Server 2005 Analysis Services
Product Version : 9.00.1399.06
Uninstall : Failed
Log File : C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_AS.log
Last Action : SetInstanceProperty
Error String : The setup has encountered an unexpected error while
Setting Internal Properties. The error is: Fatal error during
installation.
Error Number : 29528
----
--
SQL Server Setup failed. For more information, review the Setup log
file in %ProgramFiles%\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Summary.txt.
Time : Tue Mar 07 08:52:38 2006
List of log files:
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_Core(Local).log
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_AS.log
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_Datastore.xml
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_.NET Framework 2.0.log
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_Core.log
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Summary.txt
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_.NET Framework 2.0
LangPack.log
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_.NET Framework Upgrade
Advisor.log
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_.NET Framework Upgrade
Advisor LangPack.log
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_.NET Framework Windows
Installer.log
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_.NET Framework Windows
Installer LangPack.log
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_Support.log
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_SCC.log
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^^^^^^^^^^^^^^^
And also, there is no article on MS KB on how to uninstall SQL 2005
manually; there is only an article on SQL 2000.|||Hi
It appears that it is analysis services that is failing to uninstall, what
did SQLSetup0028_CGI-EDM02_AS.log say?
I was referring to the additional information in the setup help file about
removing SQL 2005 not the KB.
John
"Calvin.Lai@.shaw.ca" wrote:

> This is what C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Summary.txt is saying:
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^^^^^^^^^^
> Microsoft SQL Server 2005 9.00.1399.06
> ==============================
> OS Version : Microsoft Windows Server 2003 family, Enterprise
> Edition Service Pack 1 (Build 3790)
> Time : Tue Mar 07 08:52:10 2006
> Machine : CGI-EDM02
> Product : Analysis Services
> Error : The setup has encountered an unexpected error while
> Setting Internal Properties. The error is: Fatal error during
> installation.
> ----
--
> Machine : CGI-EDM02
> Product : Microsoft SQL Server 2005 Analysis Services
> Product Version : 9.00.1399.06
> Uninstall : Failed
> Log File : C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_AS.log
> Last Action : SetInstanceProperty
> Error String : The setup has encountered an unexpected error while
> Setting Internal Properties. The error is: Fatal error during
> installation.
> Error Number : 29528
> ----
--
>
> SQL Server Setup failed. For more information, review the Setup log
> file in %ProgramFiles%\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Summary.txt.
>
> Time : Tue Mar 07 08:52:38 2006
>
> List of log files:
> C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_Core(Local).log
> C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_AS.log
> C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_Datastore.xml
> C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_.NET Framework 2.0.log
> C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_Core.log
> C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Summary.txt
> C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_.NET Framework 2.0
> LangPack.log
> C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_.NET Framework Upgrade
> Advisor.log
> C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_.NET Framework Upgrade
> Advisor LangPack.log
> C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_.NET Framework Windows
> Installer.log
> C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_.NET Framework Windows
> Installer LangPack.log
> C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_Support.log
> C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_SCC.log
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^^^^^^^^^^^^^^^^^
> And also, there is no article on MS KB on how to uninstall SQL 2005
> manually; there is only an article on SQL 2000.
>|||Anyone?|||Calvin.Lai@.shaw.ca wrote:
> Anyone?
I ran into this issue, the box was rebooted durning the uninstall of
anlysis services, when it came back up - i tried to uninstall analysis
services / sql server 2005 - and could not
I then tried to uninstall the SQL 2005 backword combatiblity - it
uninstalled, and said analysis services is suspened, to continue it
will unsuspend, it did, and uninsalled ok, but i still run into issues
uninstalling anlysis services, in the log everything the uninstall
looks for is not there, but the service is still there - in the
services console.
any ideas?|||Usually the SQL 2K5 registry need to be deleted and the associated
files.
Do this at your own risk. If you are experimenting, this is the way to
go.
Do not quote me...
Those who dare will survive...

Can't uninstall SQL 2005

When I try to uninstall it, I get
The setup has encountered an unexpected error while Setting Internal
Properties. The error is: Fatal error during installation.
There's an OK button which I click on it and then the uninstallation
quits. Any ideas?
Hi
Check the log file in Setup Bootstrap\LOG and Setup Bootstrap\LOG\Files.
There are instructions on what the log files are in the topic "How to: View
SQL Server 2005 Setup Log File" in the Setup help files found in found in the
\Setup\help\XXXX or \Setup Bootstrap\help\XXXX directory (XXXX = language
identifier) Also check out "How to: Uninstall an Existing Instance of SQL
Server 2005 (Setup)" which will give you instruction on how to manually
remove SQL Server.
John
"Calvin.Lai@.shaw.ca" wrote:

> When I try to uninstall it, I get
> The setup has encountered an unexpected error while Setting Internal
> Properties. The error is: Fatal error during installation.
> There's an OK button which I click on it and then the uninstallation
> quits. Any ideas?
>
|||This is what C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Summary.txt is saying:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Microsoft SQL Server 2005 9.00.1399.06
==============================
OS Version : Microsoft Windows Server 2003 family, Enterprise
Edition Service Pack 1 (Build 3790)
Time : Tue Mar 07 08:52:10 2006
Machine : CGI-EDM02
Product : Analysis Services
Error : The setup has encountered an unexpected error while
Setting Internal Properties. The error is: Fatal error during
installation.
Machine : CGI-EDM02
Product : Microsoft SQL Server 2005 Analysis Services
Product Version : 9.00.1399.06
Uninstall : Failed
Log File : C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_AS.log
Last Action : SetInstanceProperty
Error String : The setup has encountered an unexpected error while
Setting Internal Properties. The error is: Fatal error during
installation.
Error Number : 29528
SQL Server Setup failed. For more information, review the Setup log
file in %ProgramFiles%\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Summary.txt.
Time : Tue Mar 07 08:52:38 2006
List of log files:
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_Core(Local).log
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_AS.log
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_Datastore.xml
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_.NET Framework 2.0.log
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_Core.log
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Summary.txt
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_.NET Framework 2.0
LangPack.log
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_.NET Framework Upgrade
Advisor.log
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_.NET Framework Upgrade
Advisor LangPack.log
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_.NET Framework Windows
Installer.log
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_.NET Framework Windows
Installer LangPack.log
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_Support.log
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_SCC.log
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
And also, there is no article on MS KB on how to uninstall SQL 2005
manually; there is only an article on SQL 2000.
|||Hi
It appears that it is analysis services that is failing to uninstall, what
did SQLSetup0028_CGI-EDM02_AS.log say?
I was referring to the additional information in the setup help file about
removing SQL 2005 not the KB.
John
"Calvin.Lai@.shaw.ca" wrote:

> This is what C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Summary.txt is saying:
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> Microsoft SQL Server 2005 9.00.1399.06
> ==============================
> OS Version : Microsoft Windows Server 2003 family, Enterprise
> Edition Service Pack 1 (Build 3790)
> Time : Tue Mar 07 08:52:10 2006
> Machine : CGI-EDM02
> Product : Analysis Services
> Error : The setup has encountered an unexpected error while
> Setting Internal Properties. The error is: Fatal error during
> installation.
> ----
> Machine : CGI-EDM02
> Product : Microsoft SQL Server 2005 Analysis Services
> Product Version : 9.00.1399.06
> Uninstall : Failed
> Log File : C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_AS.log
> Last Action : SetInstanceProperty
> Error String : The setup has encountered an unexpected error while
> Setting Internal Properties. The error is: Fatal error during
> installation.
> Error Number : 29528
> ----
>
> SQL Server Setup failed. For more information, review the Setup log
> file in %ProgramFiles%\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Summary.txt.
>
> Time : Tue Mar 07 08:52:38 2006
>
> List of log files:
> C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_Core(Local).log
> C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_AS.log
> C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_Datastore.xml
> C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_.NET Framework 2.0.log
> C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_Core.log
> C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Summary.txt
> C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_.NET Framework 2.0
> LangPack.log
> C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_.NET Framework Upgrade
> Advisor.log
> C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_.NET Framework Upgrade
> Advisor LangPack.log
> C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_.NET Framework Windows
> Installer.log
> C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_.NET Framework Windows
> Installer LangPack.log
> C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_Support.log
> C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0028_CGI-EDM02_SCC.log
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> And also, there is no article on MS KB on how to uninstall SQL 2005
> manually; there is only an article on SQL 2000.
>
|||Anyone?
|||Calvin.Lai@.shaw.ca wrote:
> Anyone?
I ran into this issue, the box was rebooted durning the uninstall of
anlysis services, when it came back up - i tried to uninstall analysis
services / sql server 2005 - and could not
I then tried to uninstall the SQL 2005 backword combatiblity - it
uninstalled, and said analysis services is suspened, to continue it
will unsuspend, it did, and uninsalled ok, but i still run into issues
uninstalling anlysis services, in the log everything the uninstall
looks for is not there, but the service is still there - in the
services console.
any ideas?