Case sensitive variables SQL Express

Hi,
I suddenly ran into a serious problem. We installed a new SQL Express 2005
SP1 on a different server and now it seems to be case sensitive with the
variables in stored procedures:
----
ALTER PROCEDURE [dbo].[GetUserID] (@.UserName varchar(50))
AS
BEGIN
DECLARE @.ret bigint;
SET NOCOUNT ON;
SELECT @.ret = UserID FROM Users WHERE UserName Like @.Username;
RETURN ISNULL(@.ret,-1);
END
----
It fails on the @.Username which is declared as @.UserName
This did not happen on our other SQL Express server. It does not have SP1
either.
Please help!!
DavidHi David,
Most likely your problem is related to different instance collation on the
different servers. All identifiers for variables, GOTO labels and temp
tables are in the default collation of the instance. Probably your new
instance of SQL Server Express is installed with a case sensitive collation.
Here is how to change it if needed:
http://msdn2.microsoft.com/en-us/library/ms179254.aspx
HTH,
Plamen Ratchev
http://www.SQLStudio.com

Can't upgrade to RS SP1

I was able to install RS on my dev machine with no issues, but the SP1
upgrade package keeps crashing. I was able to upgrade our servers to
SP1, and other developers have been able to upgrade there PCs as well.
The error log says:
[Info] Calling MsiApplyPatch with szPatchPackage = c:\14763ee99882cc0c1d73512936\sp1patch.msp
and szInstallPackage = {null} and eInstallType = INSTALLTYPE_DEFAULT
and szCommandLine = RUNFROMSP1SETUP=TRUE REINSTALLMODE=romus
REINSTALL=Server_Components,RS_Server,RS_Manager,Client_Components,RS_Designer,RS_Admin_Tools,
[Info] MsiApplyPatch returned 1603
[Info] Reporting Error 1603 using Dr. Watson.
[Info] Setup exit code is 1603
Any ideas anyone?
Thanks,
BurtIs there an RSSp1msp#.log file? This log file should contain the actual
error.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Burt" <burt_5920@.yahoo.com> wrote in message
news:19e5f39f.0409151320.316d3abe@.posting.google.com...
> I was able to install RS on my dev machine with no issues, but the SP1
> upgrade package keeps crashing. I was able to upgrade our servers to
> SP1, and other developers have been able to upgrade there PCs as well.
> The error log says:
> [Info] Calling MsiApplyPatch with szPatchPackage => c:\14763ee99882cc0c1d73512936\sp1patch.msp
> and szInstallPackage = {null} and eInstallType = INSTALLTYPE_DEFAULT
> and szCommandLine = RUNFROMSP1SETUP=TRUE REINSTALLMODE=romus
>
REINSTALL=Server_Components,RS_Server,RS_Manager,Client_Components,RS_Design
er,RS_Admin_Tools,
> [Info] MsiApplyPatch returned 1603
> [Info] Reporting Error 1603 using Dr. Watson.
> [Info] Setup exit code is 1603
> Any ideas anyone?
> Thanks,
> Burt|||Daniel,
Thanks for getting back to me. The only part of the RSSp1msp#.log that
seems to contain an error is pasted below. My issues with that portion
are:
-I don't need to update my database, just the app server on my dev box
-ReportServer isn't the right name for the current database. That was
the name of the initial one we created and did not use.
-But the ReportServer database still exists and I am dbo, contrary to
what the message says.
Any addition help would be greatly appreciated.
Burt
SQL_SUCCESS_WITH_INFO (1) in SQLDriverConnectW
sqlstate=01000, level=0, state=0, native_error=5701, msg=Changed
database context to 'master'.
sqlstate=01000, level=0, state=0, native_error=5703, msg=Changed
language setting to us_english.
SQL_ERROR (-1) in SQLExecDirectW
sqlstate=08004, level=14, state=1, native_error=916, msg=Server user
'BurtsDomain\burt' is not a valid user in database 'ReportServer'.
SQL_ERROR (-1) in SQLExecDirectW. sqlstate=08004, level=14, state=1,
native_error=916, msg=Server user 'BurtsDomain\burt' is not a valid
user in database 'ReportServer'..
SQL_SUCCESS_WITH_INFO (1) in SQLDriverConnectW
sqlstate=01000, level=0, state=0, native_error=5701, msg=Changed
database context to 'master'.
sqlstate=01000, level=0, state=0, native_error=5703, msg=Changed
language setting to us_english.
SQL_ERROR (-1) in SQLExecDirectW
sqlstate=08004, level=14, state=1, native_error=916, msg=Server user
'BurtsDomain\burt' is not a valid user in database 'ReportServer'.
SQL_ERROR (-1) in SQLExecDirectW. sqlstate=08004, level=14, state=1,
native_error=916, msg=Server user 'BurtsDomain\burt' is not a valid
user in database 'ReportServer'..
Set_Sp1_Upgrade_Settings: Unexpected Database Version. Set will roll
back.
"Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message news:<eLcwTDBnEHA.1412@.tk2msftngp13.phx.gbl>...
> Is there an RSSp1msp#.log file? This log file should contain the actual
> error.
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Burt" <burt_5920@.yahoo.com> wrote in message
> news:19e5f39f.0409151320.316d3abe@.posting.google.com...
> > I was able to install RS on my dev machine with no issues, but the SP1
> > upgrade package keeps crashing. I was able to upgrade our servers to
> > SP1, and other developers have been able to upgrade there PCs as well.
> > The error log says:
> >
> > [Info] Calling MsiApplyPatch with szPatchPackage => > c:\14763ee99882cc0c1d73512936\sp1patch.msp
> > and szInstallPackage = {null} and eInstallType = INSTALLTYPE_DEFAULT
> > and szCommandLine = RUNFROMSP1SETUP=TRUE REINSTALLMODE=romus
> >
> REINSTALL=Server_Components,RS_Server,RS_Manager,Client_Components,RS_Design
> er,RS_Admin_Tools,
> > [Info] MsiApplyPatch returned 1603
> > [Info] Reporting Error 1603 using Dr. Watson.
> > [Info] Setup exit code is 1603
> >
> > Any ideas anyone?
> >
> > Thanks,
> >
> > Burt|||I don't understand why you think you don't need to update the database. SP1
requires DB updates.
You said that you changed the name of the DB. How did you do this, with
RSConfig? Setup should be using the values in the rsreportserver.config
file for connecting to the DB. If you rename the DB does RS still work?
Finally, like setup for RS, SP1 uses the user running setup to talk to the
DB. This user needs to have system Admin rights in Sql Server. Please
ensure this is the case.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Burt" <burt_5920@.yahoo.com> wrote in message
news:19e5f39f.0409170944.7c45b429@.posting.google.com...
> Daniel,
> Thanks for getting back to me. The only part of the RSSp1msp#.log that
> seems to contain an error is pasted below. My issues with that portion
> are:
> -I don't need to update my database, just the app server on my dev box
> -ReportServer isn't the right name for the current database. That was
> the name of the initial one we created and did not use.
> -But the ReportServer database still exists and I am dbo, contrary to
> what the message says.
> Any addition help would be greatly appreciated.
> Burt
>
> SQL_SUCCESS_WITH_INFO (1) in SQLDriverConnectW
> sqlstate=01000, level=0, state=0, native_error=5701, msg=Changed
> database context to 'master'.
> sqlstate=01000, level=0, state=0, native_error=5703, msg=Changed
> language setting to us_english.
> SQL_ERROR (-1) in SQLExecDirectW
> sqlstate=08004, level=14, state=1, native_error=916, msg=Server user
> 'BurtsDomain\burt' is not a valid user in database 'ReportServer'.
> SQL_ERROR (-1) in SQLExecDirectW. sqlstate=08004, level=14, state=1,
> native_error=916, msg=Server user 'BurtsDomain\burt' is not a valid
> user in database 'ReportServer'..
> SQL_SUCCESS_WITH_INFO (1) in SQLDriverConnectW
> sqlstate=01000, level=0, state=0, native_error=5701, msg=Changed
> database context to 'master'.
> sqlstate=01000, level=0, state=0, native_error=5703, msg=Changed
> language setting to us_english.
> SQL_ERROR (-1) in SQLExecDirectW
> sqlstate=08004, level=14, state=1, native_error=916, msg=Server user
> 'BurtsDomain\burt' is not a valid user in database 'ReportServer'.
> SQL_ERROR (-1) in SQLExecDirectW. sqlstate=08004, level=14, state=1,
> native_error=916, msg=Server user 'BurtsDomain\burt' is not a valid
> user in database 'ReportServer'..
> Set_Sp1_Upgrade_Settings: Unexpected Database Version. Set will roll
> back.
>
>
> "Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
news:<eLcwTDBnEHA.1412@.tk2msftngp13.phx.gbl>...
> > Is there an RSSp1msp#.log file? This log file should contain the actual
> > error.
> >
> > --
> > -Daniel
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> >
> >
> > "Burt" <burt_5920@.yahoo.com> wrote in message
> > news:19e5f39f.0409151320.316d3abe@.posting.google.com...
> > > I was able to install RS on my dev machine with no issues, but the SP1
> > > upgrade package keeps crashing. I was able to upgrade our servers to
> > > SP1, and other developers have been able to upgrade there PCs as well.
> > > The error log says:
> > >
> > > [Info] Calling MsiApplyPatch with szPatchPackage => > > c:\14763ee99882cc0c1d73512936\sp1patch.msp
> > > and szInstallPackage = {null} and eInstallType = INSTALLTYPE_DEFAULT
> > > and szCommandLine = RUNFROMSP1SETUP=TRUE REINSTALLMODE=romus
> > >
> >
REINSTALL=Server_Components,RS_Server,RS_Manager,Client_Components,RS_Design
> > er,RS_Admin_Tools,
> > > [Info] MsiApplyPatch returned 1603
> > > [Info] Reporting Error 1603 using Dr. Watson.
> > > [Info] Setup exit code is 1603
> > >
> > > Any ideas anyone?
> > >
> > > Thanks,
> > >
> > > Burt