Free 6-hour eLearning – Visual Studio 2005, Widnows Presentation Foundation, Windows Workflow Foundation, Windows Communication Foundation

Micosoft E-Learning offers a few e-learning collection (Collection 5134) on developing rich experiences with Microsoft .NET Framework 3.0 and Visual Studio 2005. This collection of 3 2-hour premium clinics teaches about the new capabilities provided by the .NET Framework 3.0. These clinics are for experienced Developers and Software Architects who are looking to adopt Microsoft's next generation technology within their solutions. Topics covered within the collection include Windows Presentation Foundation, Windows Workflow Foundation and Windows Communication Foundation.

This collection is free till the offical launch of .NET FX!

========== For more information ==========

- Collection 5134: Developing rich experiences with Microsoft .NET Framework 3.0 and Visual Studio 2005 { https://www.microsoftelearning.com/eLearning/offerDetail.aspx?offerPriceId=109340 }

List of logins with creation dates

========== SQL Server Management Studio ==========

If you have installed the *client tools* of SQL Server 2005, you can use SQL Server Management Studio to connect to your SQL Server, open the security node, and right click to apply filter settings for showing the logins. There exists a filter criterion for login creation date.

You can also view the list of logins in the summary page (View –> Summary).

–> SQL Server Management Studio
   –> Object Explorer
      –> (+) your SQL Server
         –> (+) Security
            –> (+) Logins
–> right click for filter settings
or, –> View –> Summary –> List (login names and creation dates are shown)

========== sys.server_principals ==========

Login information can also be obtained from the catalog views of SQL Server.
- sys.server_principals contains a row for every server-level principal

- master..syslogins in SQL Server 2000

- sys.syslogins in SQL Server 2005 (for backward compatibility)

SELECT
               
'Server[@Name='
                        + quotename(CAST(serverproperty(N'Servername') AS sysname),'''')
                        + ']'
                        + '/Login[@Name='
                        + quotename(log.name,'''')
                        + ']' AS [Urn]
               
, log.name AS [Name]
               
, CASE WHEN N'U' = log.type THEN 0
                        WHEN N'G' = log.type THEN 1
                        WHEN N'S' = log.type THEN 2
                        WHEN N'C' = log.type THEN 3
                        WHEN N'K' = log.type THEN 4
                        END AS [LoginType]
               
, log.is_disabled AS [IsDisabled]
               
, log.create_date AS [CreateDate]
       
FROM
               
sys.server_principals AS log
       
WHERE
               
(log.type in ('U', 'G', 'S', 'C', 'K')
                        AND log.principal_id not between 101 and 255
                        AND log.name <> N'##MS_AgentSigningCertificate##')
       
ORDER BY
               
[Name] ASC

========== For more information ==========

- sys.server_principals (Transact-SQL)
http://msdn2.microsoft.com/en-us/library/ms188786.aspx

- syslogins
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_sys-l_64mr.asp

Enabling xp_cmdshell in SQL Server 2005

xp_cmdshell is used to spawn a Windows command shell and executes a command line process by the operating system.


In order to minimize the security risk of executing malicious code outside SQL Server 2005, xp_cmdshell is disabled by default, and the following error message will be shown when xp_cmdshell is being executed.


Msg 15281, Level 16, State 1, Procedure xp_cmdshell, Line 1
SQL Server blocked access to procedure ‘sys.xp_cmdshell’ of component ‘xp_cmdshell’ because this component is turned off as part of the security configuration for this server. A system administrator can enable the use of ‘xp_cmdshell’ by using sp_configure. For more information about enabling ‘xp_cmdshell’, see “Surface Area Configuration” in SQL Server Books Online.


(*Only* when there is an absolute need to enable the xp_cmdshell option) xp_cmdshell can be enabled by either one of the following methods.


[1] Using the Surface Area Configuration tool (or using the “sac” utility for surface area configuration)


Surface Area Configuration application can be found on the SQL Server
–> Start
  –> Programs
    –> Microsoft SQL Server 2005
      –> Configuration Tools
        –> SQL Server Surface Area Configuration
          –> click on Surface Area Configuration for Features
            –> SQL Sever instance /Database Engine
              –> xp_cmdshell (check the “Enable xp_cmdshell” checkbox)


[2] Running the sp_configure system stored procedure (administrative login required).


– To allow advanced options to be changed.
EXEC sp_configure ‘show advanced options’, 1
GO
– To update the currently configured value for advanced options.
RECONFIGURE
GO
– To enable the feature.
EXEC sp_configure ‘xp_cmdshell’, 1
GO
– To update the currently configured value for this feature.
RECONFIGURE
GO


– To disallow advanced options to be changed.
EXEC sp_configure ‘show advanced options’, 0
GO
– To update the currently configured value for advanced options.
RECONFIGURE
GO



===== For more information =====


- xp_cmdshell (Transact-SQL)
http://msdn2.microsoft.com/en-us/library/ms175046.aspx


- Surface Area Configuration for Features (xp_cmdshell) – Database Engine
http://msdn2.microsoft.com/en-us/library/ms177290.aspx


- xp_cmdshell Option
http://msdn2.microsoft.com/en-us/library/ms190693.aspx


- sac Utility
http://msdn2.microsoft.com/en-us/library/ms162800.aspx


 


===== Other posts that point here =====


~ xp_cmdshell


http://sql-server-performance.com/community/forums/p/25032/139207.aspx