SQL 2005 Module

Hello BBH,

When configuring a SQL Server module, the master and msdb database should also be replicated on the mirror drive as they contain information about the MS SQL server configuration. If the master and msdb are not replicated, the target node will have an independent database and will not get updated with the changes that were performed on the partner node. This could be causing your user databases to go suspect as the master database has different information/states for the database.

Regards,

Emilio

Thanks Emilio,

I have a question concerning this. The SQL2005 module installation instructions that I have contains the following steps as I understand it.

1. Set up all the mirroring disks on the 1st node and attach.
2. Change the server name to a virtual SQL server name and reboot
3. Install SQL server and all the patches.
4. Restore any user database as needed.
5. Change server name back to original name
5. Repeat for the 2nd node.

The issue that I ran into following this instruction is the mirror datasource is no longer active and accessible since the server name have change and the agent can no longer start up. Therefore, I cannot put the data in the mirror drive. Did I not read the instructions right or misinterpret something?

thanks.

Hello BBH,

This appears to be a documentation error with the SQL 2005 installation steps. You may perform the steps provided, but leave the data source creation to after you have successfully installed SQL 2005 on both nodes and moved the data files. The problem is that after the reboot the data source does not automatically re-attach on the node. It is also not possible to attach the data source after the reboot, as the AutoStart agent will not restart while renamed to the virtual name.

I hope this helps and please open a support case to file the documentation bug.

Regards,

Emilio

Hi Emilio,

I reinstalled SQL server with the vritual name on both servers with the data being on the drive to be mirrored, renamed the servers back to their original name, rebooted, reinstalled Autostart 53, created the datasource and SQL module instance. The failover is still not working in that the SQL server service will not startup on the secondary node. The only way to get the service to start is copying the original data files, which I saved after the SQL install, to the mirrored drive. This, however, causes the primary node SQL server service to not startup if failed back to the primary node. Again, the only way to get it to start is copying the original data files to the mirrored drive. I think I am a step or 2 from getting it to work.

Thanks.

I have not seen this symptom in the past. This appears that it might be more involved and would suggest a support case be opened for this issue.

Emilio

hi,
When I configurate the services for SQL Server2005,and failover is conrect,but when failover to the seconed node,the application can no login the sql server2005.and when it locate the node1,application can login the database.

Is there any qustion of SQL Server2005 or AS5.3?or installation of SQL Server2005 on node2's step is wrong?

Hello David,

I have seen this occur with the SQL 2000 module when the master and msdb database were not replicated in the cluster. The master database contains all of the security information for SQL server; therefore it should be moved to the shared partition so both nodes have access to the same master database. If you already have the master database on the shared partition, verify that the SQL installation on the troubled node is pointing the master database correctly.

Emilio

Hello Emilio

I had replcated the master and msdb database.but I used the services of SQL Server Services,not the module of AS Module 1.0 for SQL Server 2005.Because
I did not know the EVAL license of the AS module 1.0 SQL Server 2005.

Can you tell me the EVAL license of the AS module 1.0 SQL Server 2005?

thanks.

Hi,

The evaluation key to SQL2005Module doesn't have the description anywhere.

I was able to obtain it by guessing the evaluation key from the experience.

evaluation key is s5eval.

Try this.

Thanks.