Viewing 8 posts - 1 through 8 (of 8 total)
I seemed to have got this working again now. I decided to change the collations used in the query so that the collation SQL_Latin1_General_CP1_CI_AS was used. This is the collation...
February 9, 2010 at 7:06 am
I have the sysadmin server role so there shouldb't be any permission issues with the temp tables. I don't really want to create proper tables for this as that seems...
February 9, 2010 at 2:16 am
Jack Corbett (1/26/2010)
January 26, 2010 at 8:33 am
Have a look at the function dbo.FloorFromRoom in different db's on the same server.
I can't see anything which would have caused an issue. The function itself is quite simple.
ALTER FUNCTION...
January 26, 2010 at 8:22 am
dave.repton (1/26/2010)
This could be a reason for the difference but would need to see exactly what was being passed...
January 26, 2010 at 8:19 am
In this proc it was RoomCode which contained incorrect data in Visual Studio. Running the proc in Management Studio gave the correct data.
The same parameters were used in both...
January 26, 2010 at 7:27 am
Heres the code of one of the stored procs that has been subject to this problem.
ALTER PROCEDURE [reports].[spTimetablingEventData]
@EnteredDateFrom as char(10),
@EnteredDateTo as char(10),
@EventTypeCode as varchar(3),
@BookedForCode as varchar(12),
@BookedByMSTCode as varchar(12),
@ActivityCode as varchar(12),
@RoomCode...
January 26, 2010 at 6:54 am
jgarcinuno (1/22/2010)
January 26, 2010 at 6:42 am
Viewing 8 posts - 1 through 8 (of 8 total)