Mirroring and Logins

I've created some SSIS packages to move logins from the Primary server to the Mirror server. But I'm having a small glitch. Lets say I have a database dbA that's mirrored. I then add a login of some sort, say userA. userA's default database is dbA. When I add that login to the mirrored server, how do I get the default database to be dbA? Currently I'm getting the following error from Alter Login:

ALTER LOGIN [userA] WITH DEFAULT_DATABASE=[dbA]

Msg 954, Level 14, State 1, Line 1
The database "dbA" cannot be opened. It is acting as a mirror database. I'm currently adding the logins with master as the default and then using Alter to attempt setting it. I can mask the error with a TRY block, but if I fail over it seems I'm going to have an issue. Any thoughts on this would be greatly appreciated.

Thanks,

Larry

I think the mirrored DB is inaccessible (just think of it never existed)

The only way I can think of to change the default DB, is to actually break the mirror (or swap Primary/Mirror role = manual failover)

alter the default databases, then re-establish the mirror (swap the role again = manual failover back to original Primary/Mirror)

|||

Thanks. I guess we'll have to implement a policy that we only add logins after hours or create a window of time for adding logins where we can take the database down a couple of times (to fail over and back). Seems a bit out there for a High Availability solution since it will increase downtime a lot compared to what we have now.

Thanks again,

Larry

sql

Migration of SQL Serve r2000 packages

Hi,

In SQL Server 2005, when I tried to migrate existing SQL Server 2000 DTS packages using Migration Wizard, I ran into the following error message.

"Index was out of range.Must be non-negative and less than the size of the collection.

Parameter name: index[mscorlib]"

Please help!

Thanks,

KP

Please take a look at this earlier thread:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=130931&SiteID=1
|||Hi there,

Can you describe the problem you're seeing in detail so we can try reproducing it and fixing it?

Thanks,
Silviu

SQL Server team|||

Please check your packages for a space before or (more likely) after the name of the package. This causes the error described.

Unfortunately this problem is not currently detected by Upgrade Advisor when it scans package names for invalid characters.

-Doug

Migration of SQL Serve r2000 packages

Hi,

In SQL Server 2005, when I tried to migrate existing SQL Server 2000 DTS packages using Migration Wizard, I ran into the following error message.

"Index was out of range.Must be non-negative and less than the size of the collection.

Parameter name: index[mscorlib]"

Please help!

Thanks,

KP

Please take a look at this earlier thread:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=130931&SiteID=1|||Hi there,

Can you describe the problem you're seeing in detail so we can try reproducing it and fixing it?

Thanks,
Silviu

SQL Server team|||

Please check your packages for a space before or (more likely) after the name of the package. This causes the error described.

Unfortunately this problem is not currently detected by Upgrade Advisor when it scans package names for invalid characters.

-Doug

Migration of DTS to SSIS

Well..

Have migrated my SQL 2000 DTS packages to SSIS packages through the package migration Wizard.Also, the hurdle to schedule it as a job has been resolved.But, the concern is the package contains entries\lins for old dataserver.

Is it possible to edit the SSIS pckage using management studio or integration services?

Please move this question to the " SQL Server Integration Services forum" .

Thanks

Migration of DTS to SSIS

Well..

Have migrated my SQL 2000 DTS packages to SSIS packages through the package migration Wizard.Also, the hurdle to schedule it as a job has been resolved.But, the concern is the package contains entries\lins for old dataserver.

Is it possible to edit the SSIS pckage using management studio or integration services?

Please move this question to the " SQL Server Integration Services forum" .

Thanks

Migration of DTS packages to SSIS

I am in a situation where we are redesigning our Datawarehouse. Currently we have our Datawarehouse in SQL 2000 and we are rebuilding from scratch in SQL 2005. This means that even though we will get the same tables but we are planning to rename each & every attribute to make it more meaningful.

The question is like this:

We can migrate the current DTS packages to SSIS but since all the ODBC connections , field names(attributes) will change is it worth it to leverages the DTS packages ?

Also we convert the julian date to gregorian date in our DTS packages but since SSIS has a feature to convert julian date it would be redundant to migrate the packages and my feeling is to create new packages in SSIS and start on a clean slate.

Is there anybody who was in such situation ?

Please advise.

Adarsh Mathur

Personally I would start with a clean slate. I think this will mean you are less likely to use DTS patterns and practices, which are often no longer the most appropriate (assuming they still work), when working in the brave new world of SSIS. Plan your ETL process, define the source to target mappings, and work from that rather using the DTS packages as the template.