Overview of SQL Server 2005 for the Database Administrator: "
Summary: This document provides an overview of new features in Microsoft� SQL Server� 2005 for database administration and database availability, scalability, and security.
On This Page
Introduction
High Availability and Scalability
Extending High Availability to All Database Applications
Minimizing the Maintenance Window
Database Development, Deployment, and Management: A Revolutionary Tool Set
Deploying SQL Server 2005
Tools for Management and Performance Tuning
Conclusion
Appendix"
Sunday, April 02, 2006
SQL Server 2005 Service Accounts
SQL Server 2005 Service Accounts: "Summary:
Are you aware that SQL Server 2005 can have up to ten services running? Working with that many service accounts can be a challenge. Steve Jones takes a look at these services and a few of the things that you will want to know before setting up SQL Server 2005. "
Are you aware that SQL Server 2005 can have up to ten services running? Working with that many service accounts can be a challenge. Steve Jones takes a look at these services and a few of the things that you will want to know before setting up SQL Server 2005. "
Yahoo! Developer Network Home - Welcome!
Yahoo! Developer Network Home - Welcome!:
Yahoo! is having developer network site, where one can get API that is used by Yahoo! in its websites. Worth looking and giving a try, to learn how its working.
Yahoo! is having developer network site, where one can get API that is used by Yahoo! in its websites. Worth looking and giving a try, to learn how its working.
Ajax (programming) - Wikipedia, the free encyclopedia
Ajax (programming) - Wikipedia, the free encyclopedia: "Ajax (programming)
From Wikipedia, the free encyclopedia
Jump to: navigation, search
Asynchronous JavaScript And XML, or its acronym, Ajax, is a Web development technique for creating interactive web applications. The intent is to make web pages to feel more responsive by exchanging small amounts of data with the server behind the scenes, so that the entire Web page does not have to be reloaded each time the user makes a change. This is meant to increase the Web page's interactivity, speed, and usability.
The Ajax technique uses a combination of:
XHTML (or HTML), CSS, for marking up and styling information.
The DOM accessed with a client-side scripting language, especially ECMAScript implementations like JavaScript and JScript, to dynamically display and interact with the information presented.
The XMLHttpRequest object to exchange data asynchronously with the web server. In some Ajax frameworks and in certain situations, an IFrame object is used instead of the XMLHttpRequest object to exchange data with the web server.
XML is commonly used as the format for transferring data back from the server, although any format will work, including preformatted HTML, plain text, JSON and even EBML. "
From Wikipedia, the free encyclopedia
Jump to: navigation, search
Asynchronous JavaScript And XML, or its acronym, Ajax, is a Web development technique for creating interactive web applications. The intent is to make web pages to feel more responsive by exchanging small amounts of data with the server behind the scenes, so that the entire Web page does not have to be reloaded each time the user makes a change. This is meant to increase the Web page's interactivity, speed, and usability.
The Ajax technique uses a combination of:
XHTML (or HTML), CSS, for marking up and styling information.
The DOM accessed with a client-side scripting language, especially ECMAScript implementations like JavaScript and JScript, to dynamically display and interact with the information presented.
The XMLHttpRequest object to exchange data asynchronously with the web server. In some Ajax frameworks and in certain situations, an IFrame object is used instead of the XMLHttpRequest object to exchange data with the web server.
XML is commonly used as the format for transferring data back from the server, although any format will work, including preformatted HTML, plain text, JSON and even EBML. "
.NET: Introducing Generics in the CLR -- MSDN Magazine, Visual Studio 2005 Guided Tour
.NET: Introducing Generics in the CLR -- MSDN Magazine, Visual Studio 2005 Guided Tour: "Generics are a shipping feature of the Microsoft� .NET Framework 2.0, and managed code is faster, more maintainable, and more robust because of it.
Generics are an extension to the CLR's type system that allow developers to define types for which certain details are left unspecified. Instead, these details are specified when the code is referenced by consumer code. The code that references the generic type fills in the missing details, tailoring the type to its particular needs. The name generics reflects the goal of the feature: to enable the writing of code while not specifying details that might limit the scope of its usefulness. The code itself is generic. I'll get more specific in just a moment.
A First Look at Generics
As with any new technology, it is helpful to ask just why it's useful. Those of you who are familiar with templates in C++ will find that generics serve a similar purpose in managed code. However, I hesitate to draw too much of a comparison between CLR generics and C++ templates because generics have some additional benefits, as well as some limitations.
Some of the strengths of CLR generics are compile-time type safety, binary code reuse, performance, and clarity. I'll briefly describe these benefits, and as you read the rest of this article, you'll understand them in more detail. As an example let's take two hypothetical collection classes: SortedList, a collection of Object references, and GenericSortedList, a collection of any typeT."
Generics are an extension to the CLR's type system that allow developers to define types for which certain details are left unspecified. Instead, these details are specified when the code is referenced by consumer code. The code that references the generic type fills in the missing details, tailoring the type to its particular needs. The name generics reflects the goal of the feature: to enable the writing of code while not specifying details that might limit the scope of its usefulness. The code itself is generic. I'll get more specific in just a moment.
A First Look at Generics
As with any new technology, it is helpful to ask just why it's useful. Those of you who are familiar with templates in C++ will find that generics serve a similar purpose in managed code. However, I hesitate to draw too much of a comparison between CLR generics and C++ templates because generics have some additional benefits, as well as some limitations.
Some of the strengths of CLR generics are compile-time type safety, binary code reuse, performance, and clarity. I'll briefly describe these benefits, and as you read the rest of this article, you'll understand them in more detail. As an example let's take two hypothetical collection classes: SortedList, a collection of Object references, and GenericSortedList
.NET Profiling: Write Profilers With Ease Using High-Level Wrapper Classes -- MSDN Magazine, April 2006
.NET Profiling: Write Profilers With Ease Using High-Level Wrapper Classes -- MSDN Magazine, April 2006: " Profiling API of the common language runtime (CLR) provides services that exceed the needs of typical function and memory profilers. The latest extensions of the Profiling API for the Microsoft� .NET Framework 2.0 increase this functionality even further. These extensions enable tools to trace not only method calls at the class level, but also data flow across assembly boundaries without the need to instrument Common Intermediate Language (CIL) code for that purpose.
However, the powerful functionality and technical details of this API compromise its simplicity and usefulness. Programming with the CLR Profiling API can be laborious and error-prone because the numerous services are organized in an interface that applies a primarily functional design at a low level of abstraction.
In this article we will present a high-level, easy-to-grasp, and easy-to-apply profiling API, based on the CLR Profiling API, that conceals the mechanisms necessary to filter elementary profiling data and to rejoin them into semantically coherent concepts. Programming with the high-level API should considerably reduce the development effort required to construct various types of tools that profile a program, as it affords an abstraction level close to that of high-level languages within the .NET Framework."
However, the powerful functionality and technical details of this API compromise its simplicity and usefulness. Programming with the CLR Profiling API can be laborious and error-prone because the numerous services are organized in an interface that applies a primarily functional design at a low level of abstraction.
In this article we will present a high-level, easy-to-grasp, and easy-to-apply profiling API, based on the CLR Profiling API, that conceals the mechanisms necessary to filter elementary profiling data and to rejoin them into semantically coherent concepts. Programming with the high-level API should considerably reduce the development effort required to construct various types of tools that profile a program, as it affords an abstraction level close to that of high-level languages within the .NET Framework."
Service Station: Migrating to WSE 3.0 -- MSDN Magazine, April 2006
Service Station: Migrating to WSE 3.0 -- MSDN Magazine, April 2006: "Major Changes in WSE 3.0
MSDN� recently published an article entitled 'What's New in WSE 3.0,' written by Mark Fussell, Lead Program Manager on the WSE team. This article summarizes the major changes and improvements to the product since WSE 2.0, including integration with the .NET Framework 2.0 and Visual Studio� 2005, simplified security through a new-and-improved policy architecture, and support for sending large amounts of data with Message Transmission Optimization Mechanism (MTOM). Additional changes include improved session management (via WS-SecureConversation), support for hosting ASMX services outside of IIS, and support for the latest WS-* specifications.
Although the WSE team tried hard to ensure backward compatibility, some of these changes affect the core programming model that you must address to update existing WSE 2.0 solutions.
The good news is, once you've migrated to WSE 3.0, you'll have more communications options. WSE 3.0 supports the latest WS-* specifications�the same ones supported by Windows� Communication Foundation (WCF)�making WSE 3.0 and WCF wire-compatible. This means WCF clients can interoperate with WSE 3.0 services and vice versa, removing the need for continued migration."
MSDN� recently published an article entitled 'What's New in WSE 3.0,' written by Mark Fussell, Lead Program Manager on the WSE team. This article summarizes the major changes and improvements to the product since WSE 2.0, including integration with the .NET Framework 2.0 and Visual Studio� 2005, simplified security through a new-and-improved policy architecture, and support for sending large amounts of data with Message Transmission Optimization Mechanism (MTOM). Additional changes include improved session management (via WS-SecureConversation), support for hosting ASMX services outside of IIS, and support for the latest WS-* specifications.
Although the WSE team tried hard to ensure backward compatibility, some of these changes affect the core programming model that you must address to update existing WSE 2.0 solutions.
The good news is, once you've migrated to WSE 3.0, you'll have more communications options. WSE 3.0 supports the latest WS-* specifications�the same ones supported by Windows� Communication Foundation (WCF)�making WSE 3.0 and WCF wire-compatible. This means WCF clients can interoperate with WSE 3.0 services and vice versa, removing the need for continued migration."
The Architecture Journal - Issue 6: Behavioral Software Architecture Language
The Architecture Journal - Issue 6: Behavioral Software Architecture Language: "Behavioral Software Architecture Language
by Behzad Karim
Summary: Software architecture is a hot keyword these days for people in our profession. It seems everyone is out to discover the true potential of the software architecture and what it can bring into play for them. The basic idea of architecture definition is to design software structure and object interaction before the detailed design phase. Although serious architecture definition is being suggested for large projects only, arguably any software construction or implementation work must be preceded by an architectural design and approval phase. Get acquainted with BASL, a language that unifies software architecture definition with software implementation (coding)."
by Behzad Karim
Summary: Software architecture is a hot keyword these days for people in our profession. It seems everyone is out to discover the true potential of the software architecture and what it can bring into play for them. The basic idea of architecture definition is to design software structure and object interaction before the detailed design phase. Although serious architecture definition is being suggested for large projects only, arguably any software construction or implementation work must be preceded by an architectural design and approval phase. Get acquainted with BASL, a language that unifies software architecture definition with software implementation (coding)."
The Architecture Journal - Best Practices for Rule-Based Application Development
The Architecture Journal: "Best Practices for Rule-Based Application Development
Dennis Merritt
Amzi! Inc.
January 2004
Summary: Takes a high level view of knowledge and looks at different types of knowledge and their mappings to executable computer code to gain insights into when and why rule engines provide advantages over conventional software development tools. "
Dennis Merritt
Amzi! Inc.
January 2004
Summary: Takes a high level view of knowledge and looks at different types of knowledge and their mappings to executable computer code to gain insights into when and why rule engines provide advantages over conventional software development tools. "
Saturday, April 01, 2006
Working with Skins and new controls in .NET 2005
I was helping the team in getting a proper UI.
We are using SKins and Themes for the same.
Getting a proper look for all controls was easy except for the following:
Grid View
Details View
Forms View
AFter a lot of experimenting and failures, I decided to get the desired look using the properties, and implement the code in Skin with changes. And it worked.
I am presenting the sample for different controls for convenience of those who need it.
Grid View, we need to give the Skin as below:
For Wizard, we need to give it as below:
For Buttons inlcuded in any of the Controls listed above, we need to mention in the source code where ever we see
or
ButtonClass is a class in the CSS file that defines the style. If this piece of code is not added, you may end up seeing small buttons on the screen.
One more thing I had found out while working is that Skin is having less effect on DetailsView.
Please correct me if I am wrong.
We are using SKins and Themes for the same.
Getting a proper look for all controls was easy except for the following:
Grid View
Details View
Forms View
AFter a lot of experimenting and failures, I decided to get the desired look using the properties, and implement the code in Skin with changes. And it worked.
I am presenting the sample for different controls for convenience of those who need it.
Grid View, we need to give the Skin as below:
For Wizard, we need to give it as below:
For Buttons inlcuded in any of the Controls listed above, we need to mention in the source code where ever we see
ButtonClass is a class in the CSS file that defines the style. If this piece of code is not added, you may end up seeing small buttons on the screen.
One more thing I had found out while working is that Skin is having less effect on DetailsView.
Please correct me if I am wrong.
Subscribe to:
Posts (Atom)
