Here is the code where it blows up, though we have similar code in another 15 db's they all work fine. Not sure why its acting up:

SET QUOTED_IDENTIFIER ON

GO

SET...

U have to use SQL Login id only. NT autntication will not work with linked servers. Make sure u have a common login on both the servers and under SECURITY...

It just throws the error 'Internal SQL Server Error':

Server: Msg 8624, Level 16, State 1, Procedure Org_UTrig, Line 198

Internal SQL Server error.

U can run setup and it should take care of the upgrade on its own. U don't need to backup/restore. But its always recommended to back all the databases before...

My bad. Sorry u had that in the code - Babu.

Its just that the mirror will be getting contineous feed from principle that's the reason to have it in 'NORECOVERY' mode.

Cheers,

Babu.

As discussed in SQL 2005 roadshow they say it might come with SP1 release. Cheers - Babu.

To what i understand based on the SQL 2005 roadshow is that u can have only 2 nodes. By your description it shows 3 nodes which is not supported. Even...

I agree with Rudy and especially with ArcServer i have personally run into issues of the same kind. Like said most of the vendor backup solutions are that good, but...

Just heard that in SQL 2005 roadshow in cincinnati. Cheers - Babu.

As you metioned there is usage difference on both the servers. 2 servers can never be the same as they might have different activites going at any given point. Most...

U can test the permissions by trying to map the other server drive to the parent server where u are creating the backup device.

Cheers,

Babu.

This might be stupid, but last i heard was that some of the system tables are no longer in the master db. Just a chek.

cheers,

babu.

Addition to previous reply, i have encountered few issues using Maint plans in SQL 7/2000. If the script is already is place and working fine its best to be left...

Ok here is the deal:

• First you need to check there is sufficient space meaning atleast 1 1/2 times the size of database.
• Try to shrink the database before you do...