Catálogo de publicaciones - libros

SQL Server 2005 has many new security enhancements, touching almost every area of SQL Server. We haven’t been able to look at everything in this chapter, but we’ve looked at the main security changes with regard to the database engine itself. In particular, we covered Surface area configuration : The disabling of certain features that could represent a security liability until they’re explicitly enabled by the DBA. Principals and securables : You learned how SQL Server 2005 supports Windows, server, and database-level principals, and how it adds an extra layer to the authorization model through schemas. Permissions : SQL Server 2005 has a far more granular permission structure than SQL Server 2000, allowing you more control over exactly what actions each user can perform. Code Access Security : You learned how you can achieve even greater control over code running in .NET assemblies using Code Access Security. Encryption : We showed you the new functions that allow you to encrypt data within T-SQL code, and the new objects representing symmetric and asymmetric keys and certificates. You also learned how you can use certificates to secure web services over SSL.

In this chapter, we’ve taken a fairly superficial look at Service Broker (out of necessity). Service Broker is a complex new message queuing technology for SQL Server, and in the space of one chapter it’s not possible to go into great depth. Instead, we’ve concentrated on the main elements of creating Service Broker applications, with a couple of reasonably practical examples to get you started with the technology as quickly as possible. In this chapter, we covered the following topics: What Service Broker is and situations it can be used in The Service Broker architecture and the new database objects for building Service Broker applications A simple, single-instance Service Broker application Service Broker routing and security A more complex, cross-instance Service Broker application

SSIS has changed significantly since SQL Server 2000. The result of this rearchitecture is a truly enterprise-ready, scalable, and extensible ETL application. In this chapter, you learned about some of the features introduced in SSIS, as well as the new integrated development environment (IDE). You learned about the new division of labor within the SSIS Designer: Control Flow and Data Flow. You examined all the tasks and features available for use both in the Control Flow and Data Flow toolboxes. You were introduced to the improved logging features, variables, and debugging features. Lastly, you reviewed how you can deploy and schedule SSIS packages as SQL Server Agent jobs. This chapter just barely scratches the surface of SSIS. Coverage of SSIS could easily fill an entire book of its own (and has certainly done so in previous versions), so be on the lookout for a future Apress title devoted to SSIS.

This chapter walked you through the new database mirroring and snapshot technologies in SQL Server 2005. Understanding how these technologies fit into your overall HA strategy is an important step in planning your SQL Server deployment. Even with database mirroring, you may need to use clustering, tape or disk backup, or replication to fill the needs of your SQL Server solutions. While mirroring is an important technology, there is more to achieving high availability with SQL Server than just implementing database mirroring.

In this chapter, you have seen how you can build subscription and publication applications with NS. The NS infrastructure makes it fast for you to build very complex applications. If you are an existing NS user, you’ll see the addition of an OLAP event provider, management object model, and rules as key additions to NS. If you aren’t an NS user today, hopefully you have learned about the benefits of NS and will use it in the future in your applications that provide subscription and notification capabilities.