The following tables specify the maximum sizes and numbers of various objects defined in SQL Server components.
http://msdn.microsoft.com/en-us/library/ms143432.aspx
Showing posts with label SQL Server 2008. Show all posts
Showing posts with label SQL Server 2008. Show all posts
2008-12-28
New Security Catalog Views in SQL Server 2005/2008
SQL Server 2005 introduced the concept of securables, which are anything within SQL Server which you can assign permissions against. This includes the SQL Server itself. Microsoft did this to provide more granular access in order to customize security to what you need. But with more flexibility comes more complexity. As a result, you've got to look in a few more places to understand the permissions a given login or database user has.
The use of stored procedures for roles such as sp_helprolemember and sp_helpsrvrolemember is still necessary because some permissions are assigned directly to the roles. Some roles, like db_datareader and db_datawriter, have implicit rights that will need to be taken into account. Those should stay a staple of your toolset when trying to determine security within SQL Server. The reason sp_helprotect is no longer viable at the database level is because it is included for backward compatibility and therefore only reports on those securables that were present in SQL Server 2000, such as tables, views, functions, and the like. Newer securables, such as schemas and databases, weren't in SQL Server 2000 and as a result, sp_helprotect won't report permissions on them because it doesn't report against any securable that wasn't present in SQL Server 2000.
http://www.mssqltips.com/tip.asp?tip=1653
The use of stored procedures for roles such as sp_helprolemember and sp_helpsrvrolemember is still necessary because some permissions are assigned directly to the roles. Some roles, like db_datareader and db_datawriter, have implicit rights that will need to be taken into account. Those should stay a staple of your toolset when trying to determine security within SQL Server. The reason sp_helprotect is no longer viable at the database level is because it is included for backward compatibility and therefore only reports on those securables that were present in SQL Server 2000, such as tables, views, functions, and the like. Newer securables, such as schemas and databases, weren't in SQL Server 2000 and as a result, sp_helprotect won't report permissions on them because it doesn't report against any securable that wasn't present in SQL Server 2000.
http://www.mssqltips.com/tip.asp?tip=1653
2008-09-17
Free e-book offer: Introducing Microsoft SQL Server 2008 by Peter DeBetta, Greg Low and Mark Whitehorn
Introducing Microsoft SQL Server 2008 by Peter DeBetta (ISBN: 9780735625587)
In this initial installment of the e-book, learn about some of the major new features in SQL Server 2008, including security, administration, and performance.
Register to download the free e-book, Introducing Microsoft SQL Server 2008
In this initial installment of the e-book, learn about some of the major new features in SQL Server 2008, including security, administration, and performance.
Register to download the free e-book, Introducing Microsoft SQL Server 2008
2008-04-23
Virtual TechDays
Das Info-Material (Recorded Sessions and Presentations) für Virtual TechDays vom 9. und 10. April 2008 kann unter folgende URL heruntergeladen werden:
http://www.microsoft.com/india/virtualtechdays/
Die Themen waren:
Windows Server 2008
SQL Server 2008 - Business Intelligence and Admin
SQL Server 2008-RDBMS
Visual Studio 2008 Fundamentals
SQL Server 2008 High Availability & Security
Visual Studio 2008 Web Applications
Visual Studio 2008 Smart Clients
Subscribe to:
Posts (Atom)