Estupendo articulo sobre como implantar seguridad a nivel de fila o columna en sql server 2005

Es de pago, pero es una solución.

Alucinante, recomendado.

 

 

The SQL Server group at Microsoft has just launched the SQL Server Hosting Toolkit with the release of the Database Publishing Wizard Community Technology Preview 1.

The objective of the SQL Server Hosting Toolkit is to enable a great experience around hosted SQL Server.  The Database Publishing Wizard works toward this mission by making it easy to upload a database from a development box up to a shared hoster.  In its first incarnation, the Database Publishing Wizard is a command line tool that generates a T-SQL script designed to be executed in the script execution windows provided by most hosters in their database management consoles.  In the coming months we'll be adding a GUI and building seamless integration between the tool and an upload service we'll provide to hosters for deployment.

Details on the Database Publishing Wizard as well as the download can be found at http://www.codeplex.com/Wiki/View.aspx?ProjectName=sqlhost&title=Database%20Publishing%20Wizard.

Sql Server everywhere corre en casi cualquier dispositivo que tenga alguna versión de windows, ademas proporciona el mismo subset de features corra donde corra, este sincronizador permite sincronizar una BD de access con el sql everywhere por ejemplo desde un escritorio con XP a una PDA con SQL Everywhere.

 

Como sabeis service bloker de SQL server es un sistema que nos permite generar colas como en MSMQ pero con SQL Server 2005, el trabajo con esas colas se realiza con T-SQL.

 

En esta pagina se pueden encontrar algunos ejemplos:

 

SQL Server 2005 Service Pack 2 is coming out soon. The very important piece of SP2 is support of SSRS and SharePoint 2007 Integration. There are many bug fixes and enhancements in the service pack but here I want to highlight the integration with SharePoint 2007.

The key functionalities include:

SSRS & SharePoint Integration

The existing integration between Reporting Service and SharePoint are very limited. It is primarily done through two web parts – Report Explorer for listing the reports and Report Viewer for execution of the report. Security, Management of the UI and others are not integrated. In this coming Service Pack 2, SSRS not only starts to support SharePoint 2007 which is coming out before end of this year as part of Office 2007 product release, it also enhances the degree of the integrations.

• Seamless integration with SharePoint Document Library in Office SharePoint Server 2007
  • Report server namespace and security is hosted in WSS content database
  • SharePoint database stores Report Server reports, data sources, models, resources etc.
  • Report Server database used for additional metadata (schedules, caching, subscriptions)
  • Enables collaboration, workflow, versioning
• Centralized user interface for Report Management through Office SharePoint Server 2007
  • Upload, manage, render and deliver Reports all through Office SharePoint Server 2007 UI
  • Administration using Office SharePoint Server 2007
• Rich reporting experience to "light up" Office SharePoint Server 2007
  • Filter web parts enhancing dashboards in Office SharePoint Server 2007

In SP2, Reporting Service also integrates with Hyperion, and Report Builder supports for Oracle Data Sources.

Sacado de: http://blogs.msdn.com/williaml/archive/2006/10/13/reporting-service-updates-in-sql-2005-service-pack-2.aspx

 

• Support for NAS database files with SQL Server
  You can configure SQL Server to store a database on a networked server or NAS storage server. You need to enable trace flag 1807 before you can achieve this. For more information on setting up NAS with SQL Server, refer to KB 304261.
   
• Are there any issues with NAS that I need to be aware of?
  Before you decide to run your database files on NAS, make yourself aware of the performance and database consistency considerations for using NAS. These considerations are documented in detail at KB 304261.
   
• What does Microsoft recommend – SAN or NAS?
  Because of the risks of network errors compromising database integrity, together with possible performance implications that may result from the use of network file shares to store databases, Microsoft recommends that you store database files either on local disk subsystems or on Storage Area Networks (SANs).
  
  Refer to KB 304261 for more information on this.
   
• Does Microsoft certify any hardware that works with SQL Server?
  Microsoft does not certify or validate that third-party products will work correctly with Microsoft SQL Server. Additionally, Microsoft does not provide any warranty, guaranty, or statement of any third-party product's fitness for use with SQL Server. This policy applies to hardware and software products. It is up to the third-party vendor of the product to provide any such warranty, guaranty, or statement of the product's fitness for use.
  
  For more information, please refer to KB 913945.
   
• If Microsoft doesn’t certify any third party hardware, how do I feel confident that I am running on good hardware?
  SQL Server 2005 software works on the hardware certified for use with the Microsoft Windows operating system. 
  
  Any such hardware that is certified to work with Windows is posted at Products Designed for Microsoft Windows - Windows Catalog and HCL. You can use these hardware products from third party vendors with SQL Server. 

 

No hace falta que diga las razones, que son muchas.

 

Lo que si quiero comentar es la estupenda utilidad de migración SSMA v2.0 que Microsoft nos ofrece gratuitamente.

 

La herramienta nos permite migrar las bases de datos, tanto en lo que a esquema se refiere como en los datos contenidos en las bases de datos.

 

La conversión de PLSQL en TSQL es asombrosa, triggers, SPs , funciones, etc.

 

Si teneis Oracle, instalar la herramienta y un entorno de pruebas con SQL 2005 y vosotros mismos vereis las ventajas de administración y como el rendimiento es cuanto menos equivalente.

 

 

Ademas microsoft ofrece un descuento en licencias del 50% si migras desde Oracle.

 

 

 

Lo primero que hay que leer.

Y despues te contestas las preguntas que te han surgido en:

 

Consejos:

 

Piensa que la red puede ser muy importante segun el tipo de mirroring que configures.

El mirroring no es como el log shipping, segun al configuración puede necesitar de una especie de two face commit asi que tu servidor de producción se tendra que esperar a que el servidor de respaldo indique que ya se ha realizado la transacción, asi que si los servidores tendran que estar dimensionados para soportarlo.

Se puede intalar en cluster, incluso un nodo puede replicar al otro.

Piensa que si se hace una operación en la BD el mirror la contendra tambien, por lo que para volver atras tendras que reponer un backup, no es como un logshipping que dado el retraso te puede arreglar una situación como esta.

Tampoco te vale como replica, solo como alta tolerancia.

Usar un Witness esta muy bien y queda muy bien en las arquitecturas, pero piensa en las consecuencias que tendria que por un fallo de red de 2 minutos 6000 clientes cambiaran de servidor de base de datos.

Antes de ponerlo en producción simulalo y trata de probar todas las situaciones que se te ocurran, para estar preparado para cualquier contingencia.

 

 

Ultra alta disponibilidad para SQL Server.

¿para cuando el grid de sql? :-D

 

 

Microsoft SQL Server 2005 Everywhere Edition Access Database Synchronizer