Viewing 15 posts - 76 through 90 (of 161 total)
hi, i think it's to do with the fact that case 1 returns an int, and case 2 returns a varchar,
i tweaked it to the following (basically returning case...
April 19, 2006 at 3:53 am
Eoin,
I'll mail you the scripts and some instructions for you to have a play with
Paul
November 21, 2003 at 5:48 am
hi there were some scripts in the SQL Server 7.0 Back office resource kit that implemented log shipping (a few tables and stored procedures) that we used to implement log...
November 21, 2003 at 5:21 am
sorry , i meant log shipping !
November 20, 2003 at 8:21 am
i think log shiiping is one thing that is in the enterprise edition but not standard.
Paul
November 20, 2003 at 8:20 am
I guess i'm still old-fashioned !
Paul
November 20, 2003 at 8:02 am
just use select @@version through Query Analyser
Paul
November 20, 2003 at 7:55 am
Hi,
always make sure that your backup and maintenance jobs are scheduled and work successfully in case of any problems (especially on production machines).
Paul
November 19, 2003 at 7:30 am
i was wondering whether your index wasn't considering all 11 columns (due to the 900 byte limit), and this was introducing duplicates (i.e. the first 7 columns only are being...
November 18, 2003 at 2:26 am
hi,
yes you can do this, we have several SQl Server 7.0 servers on windows 2000
Paul
November 18, 2003 at 1:49 am
Hi,
from BOL :-
The maximum number of bytes in any key cannot exceed 900 in SQL Server 2000. You can define a key using variable-length columns whose maximum sizes add...
November 17, 2003 at 9:44 am
or could you not create an empty database, and copy the log file to the location of the incorrect log ? This may trick the server into thinking that the...
November 13, 2003 at 10:03 am
can you not attach it as a different name ?
November 13, 2003 at 9:57 am
if you haven't detached the database from the target server (so that it doesn't exist on the target server ) , i don't think sp_attach_single_file_db will work.
Paul
November 13, 2003 at 9:51 am
we had a similar error. We somehow had a duplicate row in the table. we had to remove the duplicate and then the DBCC ran clean.
HTH
Paul
November 12, 2003 at 2:32 am
Viewing 15 posts - 76 through 90 (of 161 total)