Could be that the Severity level of the error that you are raising is to low (you can read about the serverity levels in books on line). ...

For each bookID there were few records with different rating. The op wanted to first key in the order by clause to be the maximum rating that the same...

You need to find the max rating for each bookid. Then you can use this number as the first key in the order by clause. Here is an...

The catch block already handled the error, so it will not be sent farther to the calling application. You have few options. You can use the return value...

You can use raiserror to raise your own error. It will behave just like any runtime error:

use tempdb

go

create proc demo (@variable int)

as

BEGIN TRY

...

Did you remember to modify the max server memory configuration?

Adi

Yes, I meant create database for attach and not create table for attach....

If I remember correctly sp_attach_db can work with less the 20 files (I think that the limit is about 16, but I'm not sure about it). You can use...

It won’t cause any problems, but the question is why do you want to shrink it? If you did something new such as changed the time interval between log...

No one can know the impact on the performance. It depends on to many factors that we don’t know. For example – The type of encryption that you’ll...

As far as I know SQL Server 32 bit can not use more then 2 GB without any special configuration. If you modify the boot.ini and add the /3GB...

It sounds like you can use replication. Have a look at BOL about transactional replication to see it this is what you need.

Adi

One way that I can think about is to create a temporary table, then use a stored procedure that works with the linked servers. It can connect to all...

You can execute extended stored procedure, but I wouldn't go that path. I would redesign the process.

Adi

This also won’t work...