 | |
Membership download
microsoft.public.sqlserver.dts microsoft.public.sqlserver.dts
 |
| | Thread Tools | Display Modes |
#51
 
| |||
| |||
|
Re: Membership download -
03-19-2008
, 09:57 PM
|
Hi Jrl, SSIS task does not include the property for ALTER AUTHORIZATION ON SCHEMA. That is just one way for your manually resolving conflictions. Backup/restore is a common way for data transfer, however it still does not include transferring logins. Before SSIS task, we often recommend customers referring to this KB article to perform the whole process: How to move databases between computers that are running SQL Server http://support.microsoft.com/?id=314546 With SSIS transfer object task, if your destination server has no logins, user roles etc same as your source server, you can perform a straight transfer; otherwise you need to first manually resolve the confliction or just transfer database objects without users, logins, roles etc. If you are familiar with .NET development, you may consider using SMO assemblies to develop an application for transferring data between databases. This can give you some custom functions. By this method, you can implement confliction revolving logic in your custom functions. For example, you can check logins on your source server and destination server, for those logins not existed on your destination server, you can directly transfer the logins; for those same logins, do not transfer them, but after the transfer completes, apply the related permissions to those same logins on the new database. You may refer to: Transfer Class http://technet.microsoft.com/es-es/l....management.sm o.transfer.aspx Regarding this issue, I think that we can make a conclusion now. Actually there is no straight way to fully satisfy your requirements in a SSIS task; however you can develop an .NET application by using SMO assemblies for resolving the complex requirements. If you have any other questions or concerns, please feel free to let me know. Best regards, Charles Wang Microsoft Online Community Support ================================================== ======= Delighting our customers is our #1 priority. We welcome your comments and suggestions about how we can improve the support we provide to you. Please feel free to let my manager know what you think of the level of service provided. You can send feedback directly to my manager at: msdnmg (AT) microsoft (DOT) com. ================================================== ======= This posting is provided "AS IS" with no warranties, and confers no rights. ================================================== ======= |
#52
| |||
| |||
|
|
Hi Jrl, SSIS task does not include the property for ALTER AUTHORIZATION ON SCHEMA. That is just one way for your manually resolving conflictions. Backup/restore is a common way for data transfer, however it still does not include transferring logins. Before SSIS task, we often recommend customers referring to this KB article to perform the whole process: How to move databases between computers that are running SQL Server http://support.microsoft.com/?id=314546 With SSIS transfer object task, if your destination server has no logins, user roles etc same as your source server, you can perform a straight transfer; otherwise you need to first manually resolve the confliction or just transfer database objects without users, logins, roles etc. If you are familiar with .NET development, you may consider using SMO assemblies to develop an application for transferring data between databases. This can give you some custom functions. By this method, you can implement confliction revolving logic in your custom functions. For example, you can check logins on your source server and destination server, for those logins not existed on your destination server, you can directly transfer the logins; for those same logins, do not transfer them, but after the transfer completes, apply the related permissions to those same logins on the new database. You may refer to: Transfer Class http://technet.microsoft.com/es-es/l....management.sm o.transfer.aspx Regarding this issue, I think that we can make a conclusion now. Actually there is no straight way to fully satisfy your requirements in a SSIS task; however you can develop an .NET application by using SMO assemblies for resolving the complex requirements. If you have any other questions or concerns, please feel free to let me know. Best regards, Charles Wang Microsoft Online Community Support ================================================== ======= Delighting our customers is our #1 priority. We welcome your comments and suggestions about how we can improve the support we provide to you. Please feel free to let my manager know what you think of the level of service provided. You can send feedback directly to my manager at: msdnmg (AT) microsoft (DOT) com. ================================================== ======= This posting is provided "AS IS" with no warranties, and confers no rights. ================================================== ======= |
#53
| |||
| |||
|
|
Hi Jrl, SSIS task does not include the property for ALTER AUTHORIZATION ON SCHEMA. That is just one way for your manually resolving conflictions. Backup/restore is a common way for data transfer, however it still does not include transferring logins. Before SSIS task, we often recommend customers referring to this KB article to perform the whole process: How to move databases between computers that are running SQL Server http://support.microsoft.com/?id=314546 With SSIS transfer object task, if your destination server has no logins, user roles etc same as your source server, you can perform a straight transfer; otherwise you need to first manually resolve the confliction or just transfer database objects without users, logins, roles etc. If you are familiar with .NET development, you may consider using SMO assemblies to develop an application for transferring data between databases. This can give you some custom functions. By this method, you can implement confliction revolving logic in your custom functions. For example, you can check logins on your source server and destination server, for those logins not existed on your destination server, you can directly transfer the logins; for those same logins, do not transfer them, but after the transfer completes, apply the related permissions to those same logins on the new database. You may refer to: Transfer Class http://technet.microsoft.com/es-es/l....management.sm o.transfer.aspx Regarding this issue, I think that we can make a conclusion now. Actually there is no straight way to fully satisfy your requirements in a SSIS task; however you can develop an .NET application by using SMO assemblies for resolving the complex requirements. If you have any other questions or concerns, please feel free to let me know. Best regards, Charles Wang Microsoft Online Community Support ================================================== ======= Delighting our customers is our #1 priority. We welcome your comments and suggestions about how we can improve the support we provide to you. Please feel free to let my manager know what you think of the level of service provided. You can send feedback directly to my manager at: msdnmg (AT) microsoft (DOT) com. ================================================== ======= This posting is provided "AS IS" with no warranties, and confers no rights. ================================================== ======= |
#54
| |||
| |||
|
|
Hi Jrl, SSIS task does not include the property for ALTER AUTHORIZATION ON SCHEMA. That is just one way for your manually resolving conflictions. Backup/restore is a common way for data transfer, however it still does not include transferring logins. Before SSIS task, we often recommend customers referring to this KB article to perform the whole process: How to move databases between computers that are running SQL Server http://support.microsoft.com/?id=314546 With SSIS transfer object task, if your destination server has no logins, user roles etc same as your source server, you can perform a straight transfer; otherwise you need to first manually resolve the confliction or just transfer database objects without users, logins, roles etc. If you are familiar with .NET development, you may consider using SMO assemblies to develop an application for transferring data between databases. This can give you some custom functions. By this method, you can implement confliction revolving logic in your custom functions. For example, you can check logins on your source server and destination server, for those logins not existed on your destination server, you can directly transfer the logins; for those same logins, do not transfer them, but after the transfer completes, apply the related permissions to those same logins on the new database. You may refer to: Transfer Class http://technet.microsoft.com/es-es/l....management.sm o.transfer.aspx Regarding this issue, I think that we can make a conclusion now. Actually there is no straight way to fully satisfy your requirements in a SSIS task; however you can develop an .NET application by using SMO assemblies for resolving the complex requirements. If you have any other questions or concerns, please feel free to let me know. Best regards, Charles Wang Microsoft Online Community Support ================================================== ======= Delighting our customers is our #1 priority. We welcome your comments and suggestions about how we can improve the support we provide to you. Please feel free to let my manager know what you think of the level of service provided. You can send feedback directly to my manager at: msdnmg (AT) microsoft (DOT) com. ================================================== ======= This posting is provided "AS IS" with no warranties, and confers no rights. ================================================== ======= |
#55
| |||
| |||
|
|
Hi Jrl, SSIS task does not include the property for ALTER AUTHORIZATION ON SCHEMA. That is just one way for your manually resolving conflictions. Backup/restore is a common way for data transfer, however it still does not include transferring logins. Before SSIS task, we often recommend customers referring to this KB article to perform the whole process: How to move databases between computers that are running SQL Server http://support.microsoft.com/?id=314546 With SSIS transfer object task, if your destination server has no logins, user roles etc same as your source server, you can perform a straight transfer; otherwise you need to first manually resolve the confliction or just transfer database objects without users, logins, roles etc. If you are familiar with .NET development, you may consider using SMO assemblies to develop an application for transferring data between databases. This can give you some custom functions. By this method, you can implement confliction revolving logic in your custom functions. For example, you can check logins on your source server and destination server, for those logins not existed on your destination server, you can directly transfer the logins; for those same logins, do not transfer them, but after the transfer completes, apply the related permissions to those same logins on the new database. You may refer to: Transfer Class http://technet.microsoft.com/es-es/l....management.sm o.transfer.aspx Regarding this issue, I think that we can make a conclusion now. Actually there is no straight way to fully satisfy your requirements in a SSIS task; however you can develop an .NET application by using SMO assemblies for resolving the complex requirements. If you have any other questions or concerns, please feel free to let me know. Best regards, Charles Wang Microsoft Online Community Support ================================================== ======= Delighting our customers is our #1 priority. We welcome your comments and suggestions about how we can improve the support we provide to you. Please feel free to let my manager know what you think of the level of service provided. You can send feedback directly to my manager at: msdnmg (AT) microsoft (DOT) com. ================================================== ======= This posting is provided "AS IS" with no warranties, and confers no rights. ================================================== ======= |
#56
| |||
| |||
|
|
Hi Jrl, SSIS task does not include the property for ALTER AUTHORIZATION ON SCHEMA. That is just one way for your manually resolving conflictions. Backup/restore is a common way for data transfer, however it still does not include transferring logins. Before SSIS task, we often recommend customers referring to this KB article to perform the whole process: How to move databases between computers that are running SQL Server http://support.microsoft.com/?id=314546 With SSIS transfer object task, if your destination server has no logins, user roles etc same as your source server, you can perform a straight transfer; otherwise you need to first manually resolve the confliction or just transfer database objects without users, logins, roles etc. If you are familiar with .NET development, you may consider using SMO assemblies to develop an application for transferring data between databases. This can give you some custom functions. By this method, you can implement confliction revolving logic in your custom functions. For example, you can check logins on your source server and destination server, for those logins not existed on your destination server, you can directly transfer the logins; for those same logins, do not transfer them, but after the transfer completes, apply the related permissions to those same logins on the new database. You may refer to: Transfer Class http://technet.microsoft.com/es-es/l....management.sm o.transfer.aspx Regarding this issue, I think that we can make a conclusion now. Actually there is no straight way to fully satisfy your requirements in a SSIS task; however you can develop an .NET application by using SMO assemblies for resolving the complex requirements. If you have any other questions or concerns, please feel free to let me know. Best regards, Charles Wang Microsoft Online Community Support ================================================== ======= Delighting our customers is our #1 priority. We welcome your comments and suggestions about how we can improve the support we provide to you. Please feel free to let my manager know what you think of the level of service provided. You can send feedback directly to my manager at: msdnmg (AT) microsoft (DOT) com. ================================================== ======= This posting is provided "AS IS" with no warranties, and confers no rights. ================================================== ======= |
#57
| |||
| |||
|
|
Hi Jrl, SSIS task does not include the property for ALTER AUTHORIZATION ON SCHEMA. That is just one way for your manually resolving conflictions. Backup/restore is a common way for data transfer, however it still does not include transferring logins. Before SSIS task, we often recommend customers referring to this KB article to perform the whole process: How to move databases between computers that are running SQL Server http://support.microsoft.com/?id=314546 With SSIS transfer object task, if your destination server has no logins, user roles etc same as your source server, you can perform a straight transfer; otherwise you need to first manually resolve the confliction or just transfer database objects without users, logins, roles etc. If you are familiar with .NET development, you may consider using SMO assemblies to develop an application for transferring data between databases. This can give you some custom functions. By this method, you can implement confliction revolving logic in your custom functions. For example, you can check logins on your source server and destination server, for those logins not existed on your destination server, you can directly transfer the logins; for those same logins, do not transfer them, but after the transfer completes, apply the related permissions to those same logins on the new database. You may refer to: Transfer Class http://technet.microsoft.com/es-es/l....management.sm o.transfer.aspx Regarding this issue, I think that we can make a conclusion now. Actually there is no straight way to fully satisfy your requirements in a SSIS task; however you can develop an .NET application by using SMO assemblies for resolving the complex requirements. If you have any other questions or concerns, please feel free to let me know. Best regards, Charles Wang Microsoft Online Community Support ================================================== ======= Delighting our customers is our #1 priority. We welcome your comments and suggestions about how we can improve the support we provide to you. Please feel free to let my manager know what you think of the level of service provided. You can send feedback directly to my manager at: msdnmg (AT) microsoft (DOT) com. ================================================== ======= This posting is provided "AS IS" with no warranties, and confers no rights. ================================================== ======= |
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.