| SQL Server 2008 : Client Configuration |
| Client configuration is a many-leveled beast, consisting of operating system tasks such as installing protocols, application tasks such as choosing or coding to a specific Application Programming Interface (API), provider, or driver, and maintenance tasks such as configuring network settings, building connection strings |
|
| SQL Server 2008 R2 : Client Installation |
| The same operating system requirements for server installations apply to client tools and SNAC installations, with one exception: When you install SNAC by itself on top of Windows XP, only SP1 is required, and when you install SNAC on top of Windows Server 2003, SP1 is not required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SQL Server 2008 : Developing Custom Managed Database Objects (part 1) |
| The capability to run managed code presents a world of possibilities, yet these features must be leveraged appropriately. The meaning of appropriate will ultimately be the result of ongoing dialogs between database administrators and the developers who want to use the .NET Framework in SQL Server. |
|
| SQL Server 2008 : Profiler Usage Scenarios (part 2) |
| Deadlocks are a common occurrence in database management systems (DMBSs). In simple terms, deadlocks occur when a process (for example, SPID 10) has a lock on a resource that another process (for example, SPID 20) wants. |
|
|
|
| SQL Server 2008 : Defining Server-Side Traces |
| Much of the SQL Server Profiler functionality can also be initiated through a set of system stored procedures. Through these procedures, you can define a server-side trace that can be run automatically or on a scheduled basis, such as via a scheduled job, instead of through the Profiler GUI |
|
|
|
|
|
|
|
| SQL Server 2008 : SQL Server Profiler Architecture |
| SQL Server 2008 has both a server and a client-side component for tracing activity on a server. The SQL trace facility is the server-side component that manages queues of events initiated by event producers on the server. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
