Digicorp

SQL Server is great product and it has many feature which are very unique to SQL Server. Regarding feature of SQL Server where multiple variable can be declared in one statement, it is absolutely possible to do.

Method 1: Multiple statements for declaring multiple variables

DECLARE @Var1 INT
DECLARE @Var2 INT
SET @Var1 = 1
SET @Var2 = 2
SELECT @Var1 'Var1', @Var2 'Var2'
GO

Method 2: Single statements for declaring multiple variables

DECLARE @Var1 INT, @Var2 INT
SET @Var1 = 1
SET @Var2 = 2
SELECT @Var1 'Var1', @Var2 'Var2'
GO

From above example it is clear that multiple variables can be declared in one statement. In SQL Server 2008 when variables are declared they can be assigned values as well.

Reference : Pinal Dave (http://www.SQLAuthority.com)

1     Improper Input Validation
2     Improper Encoding or Escaping of Output
3     Failure to Preserve SQL Query Structure (‘SQL Injection’)
4     Failure to Preserve Web Page Structure (‘Cross-site Scripting’)
5     Failure to Preserve OS Command Structure (‘OS Command Injection’)
6     Clear text Transmission of Sensitive Information
7     Cross-Site Request Forgery (CSRF)
8     Race Condition
9     Error Message Information Leak
10   Failure to Constrain Operations within the Bounds of a Memory Buffer
11   External Control of Critical State Data
12   External Control of File Name or Path
13   Untrusted Search Path
14   Failure to Control Generation of Code (‘Code Injection’)
15   Download of Code Without Integrity Check
16   Improper Resource Shutdown or Release
17   Improper Initialization
18   Incorrect Calculation
19   Improper Access Control (Authorization)
20   Use of a Broken or Risky Cryptographic Algorithm
21   Hard-Coded Password
22   Incorrect Permission Assignment for Critical Resource
23   Use of Insufficiently Random Values
24   Execution with Unnecessary Privileges
25   Client-Side Enforcement of Server-Side Security

If you want to go through with example then please Refer below link:

http://www.softwaretestinghelp.com/top-25-common-programming-bugs-every-tester-should-know/#more-353

The My Documents folder is your own personal and Most important folder in which you can store your documents, graphics, Music and mostly default location for downloads. By default, the target or actual location of the My Documents folder is C:\Documents and Settings\user name\My Documents, where C is the drive in which Windows is installed, and user name is the currently logged-on user.

Why should we change the default location of My Document Folder ?

(1) In order to maintain data and make it easily available and keep it secure with other files.

(2) Often we forgot to backup My Document Folder Before our PC is being formatted and accidently our whole data in My Document is Erased, So this is the best practice for you to make sure that your all data is secured before formatting C Drive (System Drive).

To change the default location of the My Documents folder, follow these steps:

1.  Click Start, and then point to My Documents.

2. Right-click My Documents, and then click Properties.

3. Click the Target tab.

4. In the Target box, do one of the following:

* Type the path to the folder location that you want, and then click OK.

For example, D:\My Stuff.

* If the folder does not exist, the Create Message dialog box is

displayed. Click Yes to create the folder, and then click OK.

OR

Click Move, click the folder in which to store your documents, and then  click OK twice.

If you need to create a new folder, click Make New Folder. Type a name for the folder, and then click OK twice.

5. In the Move Documents box, click Yes to move your documents to the new location, or click No to leave your documents in the original location.

Restore the My Documents Folder to Its Default Location :

1.  Click Start, and then point to My Documents.

2. Right-click My Documents, and then click Properties.

3. Click Restore Default, and then click OK.

4. In the Move Documents box, click Yes to move your documents to the new location, or click No to leave your documents in the original location.

What is Salesforce?

Salesforce.com is a vendor of Customer Relationship Management (CRM) solutions, which it delivers to businesses over the Internet using the software as a service model.

History

Origins

Salesforce.com was founded in 1999 by former Oracle executive Mac Benioff . In June 2004, the company went public on the New York Stock Exchange under the stock symbol CRM. Initial investors in salesforce.com were Marc Benioff,Larry Ellison,Halsey Minor, Magdalena Yesil and Igor Sill, Geneva Venture Partners.

Current status

Salesforce.com is headquartered in San Francisco, California, with regional headquarters in Dublin (covering Europe, Middle East, and Africa), Singapore (covering Asia Pacific less Japan), and Tokyo (covering Japan). Other major offices are in Toronto, New York, London, Sydney, and San Mateo, California. Salesforce.com has its services translated into 16 different languages and currently has 55,400 customers and over 1,500,000 subscribers. In 2008, Salesforce.com ranked 43rd on the list of largest software companies in the world.

Products and Services

Customer Relationship Management

Salesforce.com’s CRM solution is broken down into several applications: Sales, Service & Support, Partner Relationship Management, Marketing, Content, Ideas and Analytics.

Force.com Platform

Salesforce.com’s Platform-as-a-Service product is known as the Force.com Platform. The platform allows external developers to create add-on applications that integrate into the main Salesforce application and are hosted on salesforce.com’s infrastructure.

These applications are built using Apex (a proprietary Java-like programming language for the Force.com Platform) and Visualforce (an XML-like syntax for building user interfaces in HTML, AJAX or Flex).

AppExchange

Launched in 2005, AppExchange is a directory of applications built for Salesforce by third-party developers which users can purchase and add to their Salesforce environment. As of September 2008, there are over 800 applications available from over 450 ISVs.

Customization

Salesforce users can customize their CRM application. In the system, there are tabs such as “Contacts”, “Reports”, and “Accounts”. Each tab contains associated information. For example, “Contacts” has standard fields like First Name, Last Name, and Email.

Customization can be done on each tab, by adding user-defined custom fields.

Customization can also be done at the “platform” level by adding customized applications to a Salesforce.com instance, that is adding sets of customized / novel tabs for specific vertical- or function-level (Finance, Human Resources, etc) features.

Web Services

In addition to the web interface, Salesforce offers a Web Services API that enables integration with other systems.

Mobile support

In April 2009, Salesforce released a slimmed down version of their application for subscribers with Blackberry, iPhone, and Windows mobile devices

Languages

English, Dutch, Spanish, German, French, Finnish, Swedish, Japanese, Italian, Portuguese (Brazilian), Korean, Russian, Thai, Danish, Simplified Chinese and Traditional Chinese. Application and online help & training documentation are available in these languages.

Also, end user languages are available in Hungarian, Czech, Turkish, Polish, Lithuanian, Latvian & Estonian.

Other

Other technologies in use at salesforce.com are Resin Application Server, and the in-house technologies Apex (a Java-like programming language and programming platform) and S-controls (Salesforce widgets – these are predominantly based on JavaScript).

ADVANTAGES

Cloud Computing

These new ways of building and running applications are enabled by the world of cloud computing, where you access applications, or apps, over the Internet as utilities, rather than as pieces of software running on your desktop or in the server room. This model is already quite common for consumer apps like email and photo sharing, and for certain business applications, like customer relationship management (CRM).

Force Platform is the world’s first Platform as a Service (PaaS), enabling developers to create and deliver any kind of business application in the cloud, entirely on-demand Platform App and without software

Data-Centric Apps

A data-centric app is an application that is based on structured, consistent information such as you might find in a database or an XML file.We can find these data-centric apps everywhere, in small desktop databases like Microsoft Access or FileMaker, all the way to the huge systems running on database management systems like Oracle or MySQL. Unlike applications that are built around unstructured data, like plain text documents or HTML files, data-centric apps make it easy to control, access, and manage data.

• Unparalleled time to value. Salesforce.com minimizes the risk involved in implementing business applications like CRM by eliminating the need for up-front capital investment, making the path to CRM success exceptionally short. Salesforce implementations usually take less than a month and rarely exceed three months, compared to 12 months or longer with client/server software. According to a recent study by Triple Tree and the Software and Information Industry Association (SIIA), on-demand deployments are 50 to 90 percent faster, with a total cost of ownership five to ten times less than installed software.
• Less expensive initially-and in the long run. It’s easy to see why a multitenant, on-demand solution is much less expensive initially. There is no hardware to purchase, scale, and maintain, no operating systems, database servers, or application servers to install, no consultants and staff to manage it all, and no need for periodic upgrades.
• Easy upgrades. Customers of on-demand applications benefit from instant deployment of new versions, which means the entire customer base is always on the latest version. Since customizations and integrations are maintained through upgrades, change management discussions can focus on taking immediate advantage of the new features and innovations available with each release.
• Better service delivery. Due to the on-demand model’s tremendous economies of scale and our seven-year focus on service delivery, salesforce.com can provide higher service levels than the vast majority of companies can achieve on their own. We use the best technologies, policies, and procedures to ensure security at the facilities, application, and network level; to ensure maximum uptime and continuous availability; and to provide a performance record we’re proud of. In fact, we’re the only vendor who makes performance statistics available on a public site: http://trust.salesforce.com.
• Better scalability. Successful businesses are continually changing and growing: Employee growth, transaction growth, the launching of new products and services, mergers and acquisitions, or any number of business events can dramatically and suddenly alter business needs.
• Easier to customize. Users of on-premise solutions have no choice but to wait weeks or months for even minor modifications to their applications, and in some cases their requests are never met at all. The Salesforce application was designed from the beginning to make performing basic customizations to the user interface and underlying data objects easy, so that even business users could customize in minutes, without programming. Without the burden of fulfilling constant requests for minor customizations, IT is free to concentrate on performing more advanced customizations, such as associating specific behavior with objects that can be triggered by a wide range of system events.
• Users are more satisfied and productive. A major reason on-premise deployments often fail is because of low user adoption-data that’s cluttered or difficult to get to quickly results in user resistance. Salesforce’s award-winning, easy-to-use interface has resulted in the highest user adoption rates in the industry.
• Easier for administrators. Administrators can tailor processes and define how data is viewed for different departments and work groups, while ensuring that users can access only that data for which they are authorized. Salesforce’s ease of use extends to its administration functions. In fact, Forrester named Salesforce the “#1 On-Demand CRM Solution for Administration.”
• Nurturing true value and innovation. By eliminating many of the problems related to traditional application development, the on-demand model frees developers to focus on developing solutions that deliver real business value. Salesforce.com supports developers with a host of on-demand development tools-including a point-and-click customization tool, toolkits for the most popular development environments, and the upcoming Force.com programming language-Apex-as well as the Force.com Developer Network. The Force.com community has grown rapidly, resulting in hundreds of innovative solutions that are made available to customers via the AppExchange directory, salesforce.com’s popular marketplace for pre-integrated, on-demand applications.

Disadvantages

Detractors claim that sales force management systems are:

• difficult to work with
• require additional work inputting data
• dehumanize a process that should be personal
• require continuous maintenance, information updating, and system upgrading
• costly
• difficult to integrate with other management information systems

Technologies Behind a Force Platform App

Multitenant architecture :

An application model in which all users and apps share a single, common infrastructure and code base.

Metadata-driven development model:

An app development model that allows apps to be defined as

declarative “blueprints,” with no code required. Data models, objects,forms, workflows, and more are defined by metadata.

Force PlatformWeb Services API:

An application programming interface that defines a Web service that provides direct access to all data stored in Force Platform from virtually any programming language and platform

Apex:

The world’s first on-demand programming language, which runs in the cloud on Force Platform servers

Visualforce

A framework for creating feature-rich user interfaces for apps in the cloud

Force Platform Sites

Public websites and applications that are directly integrated with your Salesforce organization-without requiring users to log in with a username and password

AppExchange directory

A Web directory where hundreds of AppExchange apps are available to Salesforce customers to review, demo, comment upon, and/or AppExchange directory install. Developers can submit their apps for listing on the AppExchange directory if they want to share them with the community.

Future

• A shift from the mainframe to client/server systems, resulting in a move from legacy systems to packaged enterprise systems.
• The rise of the PC, resulting in unprecedented user productivity-as well as a proliferation of data islands.
• The rise of the Internet and perpetual network access, which led to an information explosion and changed the way millions of people work, play, and shop.
• The emergence of Web services standards and technologies such as multitenant architectures.
• The move towards service oriented architecture (SOA) approaches by most major software vendors, making integration with back-end systems easier.
• The emergence of the on-demand model, which shifted the software market from an ownership to a “rental” model, freeing businesses from ownership hassle and expense. Salesforce.com is one of the most successful examples of this model, with 35,300 customers and more than 575 applications.

Applications Developed in Salesforce

All of the public web sites listed here have been built with Force.com Sites and run on the Force.com platform.

http://developer.force.com/sitesgallery

Currently, at digicorp we are developing an healthcare application on salesforce platform some brief overview about the application is as follows:

Used to store patient’s details like, Vital, Allergies, Medications order, Radiology order, Lab order, Referral order, Patient’s history etc. User can generate the messages for different type of orders to clerk/provider to enter into system/signoff respectively. It alos allows to store scanned documents of patients’ documents and generate the message to the provider as well. It allows to print the reports of Patient visits, orders, documents etc.

Original Content From:

http://www.salesforce.com

http://en.wikipedia.org/wiki/Salesforce.com

We have our small menu ready now, we know what all we are going to serve in Objectville. Oops, it may seem strange if you are new here in Objectville. New readers, just have a look at New Restaurant In Town and continue here. Lets prepare class for each item
Classes we need to create:

DoubleCheesePizza
ItalianPizza
FreshVeggiePizza
Vegetable Sandwich
Cheese Sandwich
Aalu-matar Sandwich

We also need to take care of our ordering system in hotel so we need one attribute called “cost” in all of the above classes. We will have descriptions of each item. Keeping in mind likings of customers, we need to have thin crust pizzas, as well as thick crust pizza. So lets have a look at these classes.

Read More >>

Basic Testing Methodology

• Unit Testing—The programmers conduct unit testing during the development phase. Programmers can test their specific functionality individually or with other units. However, unit testing is designed to test small pieces of functionality rather than the system as a whole. This allows the programmers to conduct the first round of testing to eliminate bugs before they reach the testing staff.

• Integration Testing—Incremental integration testing involves continuous testing of an application as new functionality is added. This requires that aspects of an application’s functionality be able to work separately before all parts of the application are completed. Full integration testing tests combined parts of an application to determine if they function together correctly.

• System Testing—The system is tested as a complete, integrated system. System testing first occurs in the development environment but eventually is conducted in the production environment. Dedicated testers, project managers, or other key project staff performs system testing. Functionality and performance testing are designed to catch bugs in the system, unexpected results, or other ways in which the system does not meet the stated requirements. The testers create detailed scenarios to test the strength and limits of the system, trying to break it if possible. Editorial reviews not only correct typographical and grammatical errors, but also improve the system’s overall usability by ensuring that on-screen language is clear and helpful to users. Accessibility reviews ensure that the system is accessible to users with disabilities.

• Acceptance Testing—The software is assessed against the requirements defined in the system requirements document. The user or client conducts the testing in the production environment. Successful acceptance testing is required before submitting to the client for approval.

Software Testing Types:

• Black box testing – Internal system design is not considered in this type of testing. Tests are based on requirements and functionality.
  

• White box testing – This testing is based on knowledge of the internal logic of an application’s code. Also known as Glass box Testing. Internal software and code working should be known for this type of testing. Tests are based on coverage of code statements, branches, paths, conditions.

• Unit testing – Testing of individual software components or modules. Typically done by the programmer and not by testers, as it requires detailed knowledge of the internal program design and code. May require developing test driver modules or test harnesses.

• Incremental integration testing – Bottom up approach for testing i.e continuous testing of an application as new functionality is added; Application functionality and modules should be independent enough to test separately done by programmers or by testers.

• Integration testing – Testing of integrated modules to verify combined functionality after integration. Modules are typically code modules, individual applications, client and server applications on a network, etc. This type of testing is especially relevant to client/server and distributed systems.

• Functional testing – This type of testing ignores the internal parts and focus on the output is as per requirement or not. Black-box type testing geared to functional requirements of an application.

• System testing – Entire system is tested as per the requirements. Black-box type testing that is based on overall requirements specifications, covers all combined parts of a system.

• End-to-end testing – Similar to system testing, involves testing of a complete application environment in a situation that mimics real-world use, such as interacting with a database, using network communications, or interacting with other hardware, applications, or systems if appropriate.

• Sanity testing - Testing to determine if a new software version is performing well enough to accept it for a major testing effort. If application is crashing for initial use then system is not stable enough for further testing and build or application is assigned to fix.

• Regression testing – Testing the application as a whole for the modification in any module or functionality. Difficult to cover all the system in regression testing so typically automation tools are used for these testing types.

• Acceptance testing -Normally this type of testing is done to verify if system meets the customer specified requirements. User or customer do this testing to determine whether to accept application.

• Load testing – Its a performance testing to check system behavior under load. Testing an application under heavy loads, such as testing of a web site under a range of loads to determine at what point the system’s response time degrades or fails.

• Stress testing – System is stressed beyond its specifications to check how and when it fails. Performed under heavy load like putting large number beyond storage capacity, complex database queries, continuous input to system or database load.

• Performance testing – Term often used interchangeably with ’stress’ and ‘load’ testing. To check whether system meets performance requirements. Used different performance and load tools to do this.

• Usability testing – User-friendliness check. Application flow is tested, Can new user understand the application easily, Proper help documented whenever user stuck at any point. Basically system navigation is checked in this testing.

• Install/uninstall testing - Tested for full, partial, or upgrade install/uninstall processes on different operating systems under different hardware, software environment.

• Recovery testing – Testing how well a system recovers from crashes, hardware failures, or other catastrophic problems.

• Security testing – Can system be penetrated by any hacking way? Testing how well the system protects against unauthorized internal or external access. Checked if system, database is safe from external attacks.

• Compatibility testing – Testing how well software performs in a particular hardware/software/operating system/network environment and different combination s of above.

• Comparison testing – Comparison of product strengths and weaknesses with previous versions or other similar products.

• Alpha testing – In house virtual user environment can be created for this type of testing. Testing is done at the end of development. Still minor design changes may be made as a result of such testing.

• Beta testing – Testing typically done by end-users or others. Final testing before releasing application for commercial purpose.

• Gray Box Testing - Grey box testing is the combination of black box and white box testing. Intention of this testing is to find out defects related to bad design or bad implementation of the system. In gray box testing, test engineer is equipped with the knowledge of system and designs test cases or test data based on system knowledge.
  For example, consider a hypothetical case wherein you have to test a web application. Functionality of this web application is very simple, you just need to enter your personal details like email and field of interest on the web form and submit this form. Server will get this details, and based on the field of interest pick some articles and mail it to the given email. Email validation is happening at the client side using Java Scripts.
  

When a web page is sent to the Web Server for processing, it goes through a sequence of steps before it finally gets displayed in the Web Browser.

From Web Browser to IIS

When a POST request is initiated from the client side, the Web Server traps the request and it is usually routed to an .aspx web page. The request is actually routed to the HTTP Pipeline, a chain of managed objects.

After the HTTP Page handler class is identified, the ProcessRequest() method is called which eventually fires the different page events in the life cycle of a web page.

1. Page_Init
2. LoadViewState
3. LoadPostData
4. Page_Load
5. RaisePostDataChangedEvent
6. RaisePostBackEvent
7. Page_PreRender
8. SaveViewState
9. Page_Render
10. Page_UnLoad

All these events are associated with their respective handlers and you can even override them to customize their default behavior. The following section discusses each of these events in detail.

The Page Life Cycle Events Explained

Page_Init is first event to be triggered in the page life cycle. It is responsible for the initialization activities that are essential to create a page instance. In this phase of the page life cycle, all the server controls of the web page are initialized to their default values. However, it should be noted that the View State for a page is not available at this stage of the page life cycle and a server control of the page cannot access other server controls of the page at this phase.

You can use the Page_Init event to create or re-create the controls that need to be created or re-created dynamically. The following example illustrates how you can override the OnInit() method.

protected override void OnInit(EventArgs e)
{
if (Page != null)
{
Page.Trace.Write (“The OnInit method has been called”);
base.OnInit(e);
Page.RegisterRequiresPostBack(this);
}

}

LoadViewState : “The load view state stage only happens when the page has been posted back.  During this stage the view state data saved from the previous page visit is loaded and recursively populated into the Page’s control hierarchy”. This method restores the View State information of a web page that was last saved using the SaveViewState method. You can override the LoadViewState() method to get an idea on how the viewstate is actually restored.

The following code example illustrates how you can override the LoadViewState() method.

protected override void LoadViewState(Object viewState)
{
Page.Trace.Write (“The LoadViewState method has been called.”);
if (viewState == null)
{
base.LoadViewState(viewState);
}

}

The LoadPostBackData event is fired next that processes the data that was last posted to the server for all the server controls that requires the same. Note that all controls in an ASP.NET web page is identified by a unique id. The runtime now parses the controls to match their unique ids against the Name Value Collection in the View State for the control (that has its View State enabled) and updates the control with the posted data.

The next event that gets fired is the Page_Load event that typically restores the page’s control values.

protected override void OnLoad(EventArgs e)
{

if(!IsPostBack)
{

//Code to bind static data to the controls

}

}

The RaisePostBackData and the RaisePostBackEvent events call their respective handlers if the request was a postback. The RaisePostBackEvent that executes next “notifies the server control that caused the postback that it should handle an incoming postback event.”

Pre_Render event is triggered next and you can perform any update operations that you require prior to saving the View State and rendering of the web page content.

The following code illustrates how you can override the OnPreRender() method.

protected override void OnPreRender (EventArgs e)
{  Page.Trace.Write (“The OnPreRender has been called.”);
//Any custom code
base.OnPreRender(e);
}

SaveViewState that is called next saves the View State for the web page and its controls in the hidden field called __viewstate that is associated with every web page. Note that the SaveViewMethod that is associated with the SaveViewState event returns a null reference if there is no view state associated with the control. Refer to the code snippet below that illustrates how you can override the SaveViewState() method.

protected override object SaveViewState ()
{  Page.Trace.Write (“The SaveViewState method has been called.”);
//Write your custom code here.
return base.SaveViewState();
}

The rendering event is the next stage in the web page life cycle. This actually is not an event. Rather, it is a state of processing where the Page instance executes this method on all the controls of the web page to eventually render the web page content to the web browser at the client or the requestor side.

Page_UnLoad This event is called prior to the disposal of the web page and usually contains the code that is responsible for releasing of resources that were acquired in the earlier stages of the page life cycle. Once this is done, the web browser receives the “HTTP response packet” and the web page is displayed in the web browser

The web browser now receives the HTTP response packet and displays the same in the web page. This concludes the page life cycle of an ASP.NET web page.

How can you suppress a blank sub report from displaying on the main report.

Moreover, you want to suppress the sections within a subreport, if there is no data, so that it does not display on the main report?

 For Example:

There is a subreport contained in the main report. If the subreport does not contain any data, you do not want it to display in the main report. You want to suppress the sections of the blank subreport.

 Solution

A subreport is an object within the Crystal Reports designer. Since the subreport is inserted into the main report, it cannot be entirely suppressed.

Even when a subreport does not have any records, the subreport object still exists within a section of the main report. This means the Crystal Reports designer does not consider a section that contains a subreport as a blank section.

You notice that by selecting the ‘Suppress if blank’ option, from the ‘Section Expert’ does not work.

To workaround this, you must first suppress the blank subreport, then shrink the blank section.

 Suppressing a Blank Subreport

To suppress the blank subreport, complete the following:
1. In the main report, right-click the subreport object and click ‘Edit    Subreport’. This takes you to the ‘Subreport’ tab of the main report.

2. On the ‘File’ menu, click ‘Report Options’.

3. Select the ‘Suppress Printing if No Records’ checkbox, and then click ‘OK’.

4. Return to the ‘Preview’ tab of the main report.

5. Refresh the report.
Blank subreports now appear as empty boxes on the report.

Shrinking a Blank Section

To shrink the blank section, complete the following:

1. Format the subreport object so there are no borders:

· on the main report, right-click the subreport object and click ‘Format Subreport’.

· on the ‘Borders’ tab, select ‘None’ from the Top, Bottom, Right and Left boxes.

· Click ‘OK’ to return to the report.

2. In ‘Design’ tab of the main report, resize the height of the subreport object so it is as short as possible.

3. Move the subreport object so it is at the very top of the section.

4. On the ‘Format’ menu of the main report, click ‘Section’.

5. Select the section containing the subreport, select the ‘Fit Section’ checkbox, and then

click ‘OK’ to return to the report.

Now when you preview the main report, the blank subreports are hidden from view.

Gartner, Inc. analysts highlighted the top 10 technologies and trends that will be strategic for most organizations. Factors that denote significant impact include a high potential for disruption to IT or the business, the need for a major dollar investment, or the risk of being late to adopt.

The top 10 strategic technologies for 2009 include:

Virtualization. Much of the current buzz is focused on server virtualization, but virtualization in storage and client devices is also moving rapidly.

Cloud Computing. Cloud computing is a style of computing that characterizes a model in which providers deliver a variety of IT-enabled capabilities to consumers

Servers – Beyond Blades. Servers are evolving beyond the blade server stage that exists today. This evolution will simplify the provisioning of capacity to meet growing needs.

Web-Oriented Architectures. The Internet is arguably the best example of an agile, interoperable and scalable service-oriented environment in existence.

EnterpriseMashups. Enterprises are now investigating taking mashups from cool Web hobby to enterprise-class systems to augment their models for delivering and managing applications.

Specialized Systems. Appliances have been used to accomplish IT purposes, but only with a few classes of function have appliances prevailed.

Social Software and Social Networking. Social software includes a broad range of technologies, such as social networking, social collaboration, social media and social validation.

Unified Communications. During the next five years, the number of different communications vendors with which a typical organization works with will be reduced by at least 50 percent.

Business Intelligence. Business Intelligence (BI) have a direct positive impact on a company’s business performance, dramatically improving its ability to accomplish its mission by making smarter decisions at every level of the business from corporate strategy to operational processes.

Green IT. Shifting to more efficient products and approaches can allow for more equipment to fit within an energy footprint, or to fit into a previously filled center.

Reference : Pinal Dave (http://blog.sqlauthority.com), Gartner Inc.(Published after receiving permission)

Many of us use windows remote desktop in order to connect and control remote PC or server. However, if you need to see user’s current desktop(console), we generally rely on third party tools like UltraVNC.

This feature is also available with Windows 2003 Terminal Services!! With this feature, user can connect to the console – the desktop of the actual server, rather than a terminal server session.

This is done by starting the Terminal Services client with the /console switch:

mstsc /console

However, this isn’t possible using the terminal services client that is supplied with Windows Mobile as you cannot adjust the settings of the connection.

I hope this information is helpful to you.