Viewing 15 posts - 676 through 690 (of 1,335 total)
Go for better hardware. Also use RAID levels that does not impact much on write performance.
July 10, 2007 at 5:00 am
1. Install SQL Server in new system.
2. Script out all logins in the source and run against the destination.
3. backup all user database and restore in destination.
4. script all jobs...
July 10, 2007 at 4:34 am
You can also use the procedure sp_resetstatus to recover from emergency/suspect mode.
July 10, 2007 at 4:26 am
No luck from myside BOSS. i installed a new 2005 named instance and tried with servername\instancename that worked then servername\instancename123, servername\instancename1234, servername\instancenamewert and servername\instancenameabcd all failed saying server doesn't exist....
July 10, 2007 at 4:13 am
i will just summarise it point wise
1. have browser services enabled and running
2. have local and remote tcp/named pipes enabled
3. have named pipes protocol enabled
this will prevent most connection problems.
July 10, 2007 at 3:59 am
If its a named instance then you have to specify servername\instancename to connecto to the server specifying only the server name will not help. You are having a named instance...
July 10, 2007 at 3:47 am
Do you have alais setup for the same server calling it in different names. Check that might be you have them created.
July 10, 2007 at 3:44 am
I tried the tool it's okay but with more features it will be very good as a single point to be used.
July 10, 2007 at 3:34 am
Do you mean to say that SQL 2005 have SPIDs always less than 50 no not at all still the system SPID are between the range till 50 and user...
July 10, 2007 at 3:31 am
Could you post us the error part from the error log file when you try to access using advisor. That might give more details than this.
July 10, 2007 at 3:27 am
He is using Standard Edition so onlie indexing is not possible. But he has to say what s the error that he gets when he tries to create an index...
July 10, 2007 at 3:24 am
A problem with remote transaction between 2000 and 2005 it bugged my head for almost 6 weeks to get a solution. but atlast i got that myself.
July 10, 2007 at 3:21 am
create a user named par in the 2005 server then use sp_change_users_login 'update_one','par','par'
Then try logging in that hsould work.
July 10, 2007 at 3:19 am
You have to use 3rd party tools for that. There are tools available in net.
July 10, 2007 at 3:04 am
Viewing 15 posts - 676 through 690 (of 1,335 total)