Ms Sql Server Technology Discussions

[deals2buy]

[quote name='ghazni' timestamp='1355885824' post='1302977855']
Backup chesinapudu default ga ekadiko velipotadi kada...... malli aa path nundi ela restore cheyadam...... chala rojulu ayindi oka sari backup chesanu... aapath andariki accessible undadu kada..........
[/quote]nenu eppudu backups cheyyaledu...anduke paina post vesaa...ee sari eppudaina try cheddam ani
[quote name='ghazni' timestamp='1355885939' post='1302977867']
enta mandi sp_who2 use chestaru........ sp_who2 active use cheyandi so that DB mida enta access chestunaro telustundi.....
[/quote]ya know that...inko sp_who kuda untadi ga

[deals2buy]

[b] Difference Between CURRENT_TIMESTAMP and GETDATE() – CURRENT_TIMESTAMP Equivalent in SQL Server[/b]


Well in SQL Server GETDATE() is Equivalent to CURRENT_TIMESTAMP. However, if you use CURRENT_TIMESTAMP in your select statement it will work fine.


[img]http://www.pinaldave.com/bimg/gdv.jpg[/img]
You can see in the above example – both of them returns the same value. Now let us go to next question regarding difference between GETDATE and CURRENT_TIMESTAMP. Well, the matter of the fact, there is no difference between them in SQL Server ([url="http://msdn.microsoft.com/en-us/library/ms188751.aspx"]Reference Link[/url]). CURRENT_TIMESTAMP is an ANSI SQL function, whereas GETDATE is T-SQL implementation of the same function. Both of them derive value from the operating system of the computer on which SQL Server instance is running.
Above discussion prompts another question – in this case, [i][b]what should one use GETDATE or CURRENT_TIMESTAMP?[/b][/i]
Well, this is indeed tricky and interesting question. I think I am very comfortable using the GETDATE () so I will go to use it but a matter of the fact there is no right or wrong answer. If you want to follow ancient saying “When in Rome, do as the Romans do”, I suggest using the GETDATE (), or continue using CURRENT_TIMESTAMP.

With that said, there is one very important property we all need to keep in mind. If you use CURRENT_TIMESTAMP while creating an object, they are automatically converted to GETDATE() and stored internally. To illustrate what I am suggesting here is the example -
Create a table using the following script

[color=blue]CREATE TABLE [/color][color=black][dbo].[TestTable][/color][color=gray]([/color]
[color=black][Cold2] [datetime] [/color][color=gray]NULL
) [/color][color=blue]ON [/color][color=black][PRIMARY]
GO[/color]

[color=blue]ALTER TABLE [/color][color=black][dbo].[TestTable] [/color][color=blue]ADD DEFAULT [/color][color=gray]([/color][color=magenta]CURRENT_TIMESTAMP[/color][color=gray]) [/color][color=blue]FOR [/color][color=black][Cold2]
GO[/color]

Now go to SSMS and generate the script for the table and you will notice following syntax.

[color=blue]CREATE TABLE [/color][color=black][dbo].[TestTable][/color][color=gray]([/color]
[color=black][Cold2] [datetime] [/color][color=gray]NULL
) [/color][color=blue]ON [/color][color=black][PRIMARY]
GO[/color]

[color=blue]ALTER TABLE [/color][color=black][dbo].[TestTable] [/color][color=blue]ADD DEFAULT [/color][color=gray]([/color][color=magenta]GETDATE[/color][color=gray]()) [/color][color=blue]FOR [/color][color=black][Cold2]
GO[/color]


You can notice that SQL Server have automatically converted CURRENT_TIMESTAMP to GETDATE(). I guess this gives us an idea how they behave. Now go ahead and make your choice! Do let me know which one will you use CURRENT_TIMESTAMP or GETDATE () in the comments area.

[deals2buy]

[b] SSRS In a Flash[/b]


[b] [b]What is SQL Server Reporting Services?[/b][/b]

Your manager steps off the elevator and heads straight to your desk. He never enters the DBA cubicles, so you glance suspiciously at him. You duck your head and type furiously, hoping to blend in with the computer.
"Soo..." he drawls casually once he reaches your desk. "Big Boss wants me to write a report for the CEO on how much it rains on the plains in Spain."

Too late; you’re trapped. The last time your manager received an assignment from the Big Boss, you ended up working overtime for a month.
As he plops down a thick stack of printed papers on your desk, your fears come true. "Here is that Books Online website for SQL Server Reporting Services. I'd like that report by Friday." Your eyes shoot imaginary death rays at his quickly retreating back. What are you to do now?

Well, dear DBA, you should turn to SQLServerCentral’s [i]SSRS in a Flash[/i] series, of course! The upcoming SSRS series will discuss all aspects of SQL Server Reporting Services for someone learning to build and distribute reports. Let’s start by discussing what Reporting Services is and how we use it.

[b]What is SQL Server Reporting Services?[/b]
SQL Server Reporting Services (SSRS), Microsoft’s enterprise reporting platform, is included in the SQL Server business intelligence suite, along with SQL Server Integration Services and SQL Server Analysis Services. Although SSRS fits well with the other Microsoft business intelligence products, it is also flexible enough to show data from other platforms and be integrated into other products. In either situation, the reporting side of SQL Server provides the capability to create, distribute, and manage reports to your company. An example of an SSRS report can be seen in Figure 1.
[img]http://www.sqlservercentral.com/images/5937.jpg[/img]
[b]Figure 1. Sample SSRS report[/b]

All levels of an organization can utilize reporting through SSRS. Analysts, managers, and CEOs use reports to see company information and different analyses, which help them perform their jobs more quickly and accurately. Different parties can share the analysis of one person, rather than data remaining in one silo department. SSRS reports provide a variety of options to enhance the report consumers’ experience.
[b] [b]What can you do with SSRS reports?[/b][/b]

SSRS reports allow a user to pull, manipulate, and view their data in different ways. One way that a user can see data is by querying data from multiple sources, including SQL Server and SQL Server Analysis Services. Also, a developer can create a custom data source or use an OLE DB or ODBC provider to retrieve data from other systems. The querying language depends on the particular provider, but includes variations of SQL and MDX.

Once the data is available to the report, a developer can use report items, such as tables and textboxes to display the data in different forms. The data could be sorted, grouped, or manipulated based on expressions and properties in the report item. Developers can also show the data in visual forms, including charts and gauges. To create dynamic reports for user manipulation, developers can add parameters.
To create reports, SSRS provides two report designers: Business Intelligence Development Studio (BIDS) and Report Builder. Developers typically use BIDS, while business analysts typically use Report Builder. You can see the BIDS report designer environment in Figure 2.

[img]http://www.sqlservercentral.com/images/5938.jpg[/img]
[b]Figure 2. Business Intelligence Development Studio development environment[/b]

After report design and publication, users will want to use the report that the developer created. To satisfy this need, SSRS reports can be rendered in HTML, Excel, PDF, or other formats. Once the report is rendered, users can flip through pages, export the report to a different format, or change parameter values to re-render the report.
To permit the developer and user to work with SSRS, the full platform is composed of multiple components to help deliver, manage, and administrate the reports.
[b] [b]What components does SSRS use?[/b][/b]

The components that SSRS uses depend on which integration mode is configured. SSRS uses one of two different modes: SharePoint integrated mode or Native mode. SharePoint integrated mode allows SSRS to store its reports, report items, and metadata in SharePoint. Along with SSRS and SharePoint, a separate add-in will need to be installed to associate the two products. Native mode only requires a SQL Server instance to store its needed information.
Let’s discuss each of the three components needed for SSRS configured to run in Native mode:[list]
[*]Report Database
[*]Report Server
[*]Report Manager
[/list]
The [i]Report Database[/i] stores the metadata of the reports, report items, and security information for SSRS. The database does need to be a SQL Server database, and it will have a different format depending on if your report server is set up to integrate with SharePoint or not. The database can be stored on the same server as the SSRS instance or on another server with other SQL Server databases.
The [i]Report Server[/i] hosts SSRS reports. A windows service and a web service handle report functionality, including rendering reports, listing report items, scheduling reports, and more.

The [i]Report Manager[/i] is a web application interface to the report server. Administrators can use this tool to manage access and the location of reports. Developers can deploy reports and set up subscriptions to deliver reports to users.
Now that we’ve seen the SSRS components, let’s look at how different individuals use SSRS.
[b]Who uses SSRS?[/b]
The beauty of SSRS is that all employees of a company can receive value from reporting. From the database administrator to the CEO to the business analyst, each employee can benefit from an SSRS report. Let’s take a look at a few scenarios to highlight the advantages of SSRS.
[i]Scenario 1: Dashboards[/i]
Dashboards show how a company fares based on the facets that the company deems important. SSRS dashboard can show both trending data and key performance indicators (KPIs). A company executive can view a dashboard to pinpoint the exact area of the company that is having trouble. By clicking on the incriminating KPI, the executive passes the information to a manager. By using SSRS, the information was readily available to the executive and manager, and the company is now in the position to fix the problem.
[i]Scenario 2: Ad-hoc analysis[/i]
Business analysts spend a majority of their time working with data. They pull data from a variety of places, mash the data together, and run calculations, all with the intent of providing answers to pressing business questions. These questions could change on an hourly basis, so it is important to be able to answer them as quickly as possible. In SSRS, an analyst can pull and show the data easily and quickly and also export to another format for distribution.

[i]Scenario 3: Administration[/i]
Last, but certainly not least, we can’t leave out the DBAs. As the administrators of SSRS, DBAs will need to be able to restrict who sees which report, as well as see who is accessing which report. They can create reports to view server statistics, database health, and execution times. Although DBAs can use SSRS to run their own reports and see who is running SSRS reports, they also use the tools to administer the SSRS instance through the Report Manager, which can be seen in Figure 3.

[img]http://www.sqlservercentral.com/images/5939.jpg[/img]
[b]Figure 3. Report Manager[/b]

[b]How do you write an SSRS report for Big Boss?[/b]
So far, we’ve seen what SSRS can provide to a developer, DBA, or an end user. We know the benefits of SSRS and the different scenarios where SSRS is applicable. We’ve seen the different components of SSRS and how to manage the report server. We have a good understanding of the purpose of SSRS.

[ChampakDas]

....GP mitram

[deals2buy]

Report Builder 3.0: Adding Matrices to Your Reports

http://www.simple-talk.com/sql/reporting-services/report-builder-3.0-adding-matrices-to-your-reports/

[deals2buy]

[size=5][b]How to use Table Variables as User Defined Functions (UDFs)[/b][/size]?


[CODE]
create function fn_ret_last_created_db() returns varchar(50)
as
begin
declare @db_info varchar(50)
declare @dbs table
( name varchar(30),
created datetime)
insert into @dbs
select top 1 name,create_date
from sys.databases
order by create_date desc
select @db_info = db.name

+' '+convert(varchar(20),db.created)
from @dbs db
return @db_info
end
--test
create database new_test_db
select dbo.fn_ret_last_created_db()
[/CODE]

[deals2buy]

[b] Eleven Challenges in Unifying Reference Data[/b]


http://www.sqlservercentral.com/articles/Reference+Data/93098/

[deals2buy]

[b] SQL Server 2012 Cluster with TempDB on Local Disk[/b]


[b] Problem[/b]

With the introduction of SQL Server 2012 Microsoft officially supports local disk TempDB in SQL Server cluster configurations. This tip will show you how to configure TempDB on a local disk when installing your SQL Server 2012 cluster. We will also discuss the benefits of using TempDB on a local disk and point out potential issues that may arise and how to avoid them.
[b] Solution[/b]

The use of local disks for TempDB allows us to have more flexibility when configuring for optimal performance. It is a common performance recommendation to create the TempDB database on the fastest storage available. With the capability to utilize local disk for TempDB placement we can easily utilize disks that are larger, have a higher rotational speed or use SSD disks. SSDs are becoming more and more common and are available in multiple form factors. PCIe board SSDs, such as FusionIO and OCZ, offer even greater potential for performance improvement as they utilize the PCIe bus to provide more throughput than would be possible going through a disk interface or HBA.
Another advantage of placing TempDB on a local disk is that it creates separate paths of traffic by having your data and log files on the SAN while TempDB is on the local disk. Whether using a PCIe SSD or traditional hard drive SSDs, operations for TempDB will bypass your HBAs. This helps TempDB operations avoid congestion or contention on a shared storage network or array.
Additionally, for geographically dispersed cluster's this is a desired feature as you no longer have to replicate TempDB between sites. This translates to increased bandwidth availability and faster failovers.
[b] Configuring SQL Server 2012 Cluster TempDB Local Directory[/b]

[b] Prerequisites[/b]

Prior to installing a clustered SQL Server instance you should already have a working Windows 2008 cluster with a shared quorum disk as well as a clustered Distributed Transaction Coordinator.
The following layout would be representative of a typical cluster install for one SQL Server 2012 instance and will be utilized for this tip. For more complex configurations you may wish to add additional cluster disks for system databases, backups, etc.

[center][b]Sample Cluster Disk Layout[/b][/center] [b][b]Disk Letter[/b][/b] [b][b]Disk Type[/b][/b] [b]Purpose[/b] C:\ Local OS System Drive T:\ Local SQL TempDB Q:\ SAN Cluster Quorum M:\ SAN Cluster DTC S:\ SAN SQL Data L:\ SAN SQL Log
[b] Installing the First SQL Server Cluster Node[/b]
[list=1]
[*]Launch setup from the SQL Server 2012 media.
[*]Start your SQL Server 2012 cluster installation by clicking [b]New SQL failover cluster installation[/b] from the Installation page.


[img]http://www.mssqltips.com/tipimages2/2817_localtempdb1.jpg[/img]
[*]Proceed through the installation steps, accepting the license, selecting the desired features, naming the instance and specifying a cluster resource group name.
[*]When you get to the Cluster Disk Selection screen select the shared cluster disks that you will use for data and log directories.


[img]http://www.mssqltips.com/tipimages2/2817_localtempdb2.jpg[/img]
[*]Continue through the installation, providing the cluster network information and service accounts.
[*]When you get to the Database Engine Configuration specify your SAN disks for the Data and Log directories. Specify the local disk for your TempDB directories.


[img]http://www.mssqltips.com/tipimages2/2817_localtempdb3.jpg[/img]

A warning indication will appear advising you to ensure that the same local path exists on every cluster node. As we will see cluster failover will fail if the exact local path is not defined on all cluster nodes.
[img]http://www.mssqltips.com/tipimages2/2817_localtempdb4.jpg[/img]
[*]Continue through the remaining cluster install steps and complete the installation.


[img]http://www.mssqltips.com/tipimages2/2817_localtempdb14.jpg[/img]
[*]When finished your disks in Windows Explorer should look as follows. Note that the Operating System and TempDB are local disks while the remainder are SAN disks.
[/list]
[img]http://www.mssqltips.com/tipimages2/2817_localtempdb5.jpg[/img]
[b] Installing Additional SQL Server 2012 Cluster Nodes[/b]

When adding additional nodes to the cluster the key is to ensure the folders are created with the same path for the local TempDB directory. The SQL Server cluster group will fail to come online if the full path is not created on the additional instance.[list=1]
[*]Launch the SQL Server 2012 setup on to the next node of your cluster, click [b]Add node to a SQL Server failover cluster[/b] on the Installation page as shown below.


[img]http://www.mssqltips.com/tipimages2/2817_localtempdb6.jpg[/img]
[*]Proceed through the Add Node steps, selecting the same settings as configured for the first node. You do not need to specify the path to any disks during an Add Node installation.
[*]Complete the installation on the additional node.
[/list]
[img]http://www.mssqltips.com/tipimages2/2817_localtempdb15.jpg[/img]
[b] SQL Server Cluster Failover Validation[/b]

You have now completed installing SQL Server 2012 on at least 2 nodes to form a cluster. The next step would be to verify cluster failover between nodes.
[list]
[*]On the first node Open the Failover Cluster Manager.
[*]Select [b]Move this service or application to a different node[/b] on the SQL Server group as shown below.


[img]http://www.mssqltips.com/tipimages2/2817_localtempdb7.jpg[/img]
[*]It is possible that the SQL Server resource and the SQL Agent resource fail to come up on the second cluster node.


[img]http://www.mssqltips.com/tipimages2/2817_localtempdb8.jpg[/img]
[*]Open the system Event Viewer to check for any messages related to the resource not coming online.
[*]You will see Error Events 5123 and 17204 in the Event Viewer Application Log.


[img]http://www.mssqltips.com/tipimages2/2817_localtempdb9.jpg[/img]
[*]These errors are related to the local path for TempDB not being created on the additional cluster node.


[img]http://www.mssqltips.com/tipimages2/2817_localtempdb10.jpg[/img]
[*]Create the same exact path for TempDB on the additional node.

[img]http://www.mssqltips.com/tipimages2/2817_localtempdb11.jpg[/img]
[*]Now attempt to move the SQL Server group to the second node again. If the same local path is available the TempDB files will be created. SQL Server will automatically apply the proper permissions to the directory.

[img]http://www.mssqltips.com/tipimages2/2817_localtempdb12.jpg[/img]
The cluster should now fail over between all nodes while utilizing local disk for TempDB on each node.


[img]http://www.mssqltips.com/tipimages2/2817_localtempdb13.jpg[/img]
[/list]

[deals2buy]

ee Question ki answer evarikaina telusa vayya?

Is it possible to create a table with unique constraint that allows multiple NULL values from SQL Server 2008 onwards?

[Sehwagante100Dhonis]

[deals2buy]

[color=#ff0000][b] Some tips for working with big data models[/b][/color]


[b] 1) Identify the biggest, the largest, and the most used tables in the model[/b]

[b] 2) Use a source control, versioning or change management tool[/b]

[b] 3) Know how to print the complete or partial database model[/b]

[b] 4) Identity the most used complementary objects (stored procedures, triggers, functions, indexes)[/b]

[b] 5) Have a way to see the database in separated layers: with and without relationships, with and without indexes, with and without constraints, etc.[/b]

[b] 6) Use colored rectangles to group related tables from the same subsystem[/b]

[b] 7) Enumerate the correct order to insert, update and remove the data in specific tables in order to respect the relationships[/b]

[b] 8) Always have a way to search for the table's name, columns, datatypes, nullability, description and other attributes[/b]

[b] 9) Have a script that generate the current database (all objects) with a fraction of its size (10% is ok)[/b]

[b] 10) Keep an updated list of the permissions for the most common and used database objects (in order to know very quickly what a specific user can and cannot do with the objects)[/b]

[b] 11) Know how to predict and estimate sizes of specific objects in order to forecast database 's growth or shrinkage.[/b]

[b] 12) Show in the database model which objects have partitioning options, if they are compressed and the filegroups they belong to.[/b]

[b] 13) In OLAP (Online Analytical Processing) models centralize the fact table and have a way to link the description of the main hierarchy, levels, members, and grains for each dimension table.[/b]


For detailed description: [url="http://www.sqlservercentral.com/articles/model/72275/"]http://www.sqlserver...es/model/72275/[/url]

[deals2buy]

[quote name='Kaarthikeya' timestamp='1356044478' post='1302990973']
ee Question ki answer evarikaina telusa vayya?

Is it possible to create a table with unique constraint that allows multiple NULL values from SQL Server 2008 onwards?
[/quote]

[b]Answer: [/b]Yes
[b]Explanation: [/b]By applying a filtered index, we can create a table with a unique constraint that allows multiple NULL values. The code below shows this:
[CODE]
USE [TEST]
GO

CREATE TABLE [dbo].[tbl_test](
[id] [int]
) ON [PRIMARY]

GO

CREATE UNIQUE NONCLUSTERED INDEX UNCI_test
ON [dbo].[tbl_test](id)
WHERE id IS NOT NULL
GO
--=======================================
insert into [dbo].[tbl_test] values(1)--success
insert into [dbo].[tbl_test] values(2)--success
insert into [dbo].[tbl_test] values(NULL)--success
insert into [dbo].[tbl_test] values(NULL)--success
insert into [dbo].[tbl_test] values(2)--error [Cannot insert duplicate key row in object 'dbo.tbl_test' with unique index 'NCI_test'.]

GO
select * from [dbo].[tbl_test]
[/CODE]

Ref: CREATE INDEX - [url="http://www.sqlservercentral.com/links/1427054/286328"]http://msdn.microsoft.com/en-us/library/ms188783%28v=sql.100%29.aspx[/url]

[deals2buy]

evaraina SQL nundi batch file ela execute cheyyalo cheppandi..other than xp_cmdshell

[9Pardhu]

[quote name='Kaarthikeya' timestamp='1356044415' post='1302990963']
[b] SQL Server 2012 Cluster with TempDB on Local Disk[/b]


[b] Problem[/b]

With the introduction of SQL Server 2012 Microsoft officially supports local disk TempDB in SQL Server cluster configurations. This tip will show you how to configure TempDB on a local disk when installing your SQL Server 2012 cluster. We will also discuss the benefits of using TempDB on a local disk and point out potential issues that may arise and how to avoid them.
[b] Solution[/b]

The use of local disks for TempDB allows us to have more flexibility when configuring for optimal performance. It is a common performance recommendation to create the TempDB database on the fastest storage available. With the capability to utilize local disk for TempDB placement we can easily utilize disks that are larger, have a higher rotational speed or use SSD disks. SSDs are becoming more and more common and are available in multiple form factors. PCIe board SSDs, such as FusionIO and OCZ, offer even greater potential for performance improvement as they utilize the PCIe bus to provide more throughput than would be possible going through a disk interface or HBA.
Another advantage of placing TempDB on a local disk is that it creates separate paths of traffic by having your data and log files on the SAN while TempDB is on the local disk. Whether using a PCIe SSD or traditional hard drive SSDs, operations for TempDB will bypass your HBAs. This helps TempDB operations avoid congestion or contention on a shared storage network or array.
Additionally, for geographically dispersed cluster's this is a desired feature as you no longer have to replicate TempDB between sites. This translates to increased bandwidth availability and faster failovers.
[b] Configuring SQL Server 2012 Cluster TempDB Local Directory[/b]

[b] Prerequisites[/b]

Prior to installing a clustered SQL Server instance you should already have a working Windows 2008 cluster with a shared quorum disk as well as a clustered Distributed Transaction Coordinator.
The following layout would be representative of a typical cluster install for one SQL Server 2012 instance and will be utilized for this tip. For more complex configurations you may wish to add additional cluster disks for system databases, backups, etc.

[center][b]Sample Cluster Disk Layout[/b][/center]
[b][b]Disk Letter[/b][/b] [b][b]Disk Type[/b][/b] [b]Purpose[/b] C:\ Local OS System Drive T:\ Local SQL TempDB Q:\ SAN Cluster Quorum M:\ SAN Cluster DTC S:\ SAN SQL Data L:\ SAN SQL Log
[b] Installing the First SQL Server Cluster Node[/b][list=1]
[*]Launch setup from the SQL Server 2012 media.
[*]Start your SQL Server 2012 cluster installation by clicking [b]New SQL failover cluster installation[/b] from the Installation page.


[img]http://www.mssqltips.com/tipimages2/2817_localtempdb1.jpg[/img]
[*]Proceed through the installation steps, accepting the license, selecting the desired features, naming the instance and specifying a cluster resource group name.
[*]When you get to the Cluster Disk Selection screen select the shared cluster disks that you will use for data and log directories.


[img]http://www.mssqltips.com/tipimages2/2817_localtempdb2.jpg[/img]
[*]Continue through the installation, providing the cluster network information and service accounts.
[*]When you get to the Database Engine Configuration specify your SAN disks for the Data and Log directories. Specify the local disk for your TempDB directories.


[img]http://www.mssqltips.com/tipimages2/2817_localtempdb3.jpg[/img]

A warning indication will appear advising you to ensure that the same local path exists on every cluster node. As we will see cluster failover will fail if the exact local path is not defined on all cluster nodes.
[img]http://www.mssqltips.com/tipimages2/2817_localtempdb4.jpg[/img]
[*]Continue through the remaining cluster install steps and complete the installation.


[img]http://www.mssqltips.com/tipimages2/2817_localtempdb14.jpg[/img]
[*]When finished your disks in Windows Explorer should look as follows. Note that the Operating System and TempDB are local disks while the remainder are SAN disks.
[/list]
[img]http://www.mssqltips.com/tipimages2/2817_localtempdb5.jpg[/img]
[b] Installing Additional SQL Server 2012 Cluster Nodes[/b]

When adding additional nodes to the cluster the key is to ensure the folders are created with the same path for the local TempDB directory. The SQL Server cluster group will fail to come online if the full path is not created on the additional instance.[list=1]
[*]Launch the SQL Server 2012 setup on to the next node of your cluster, click [b]Add node to a SQL Server failover cluster[/b] on the Installation page as shown below.


[img]http://www.mssqltips.com/tipimages2/2817_localtempdb6.jpg[/img]
[*]Proceed through the Add Node steps, selecting the same settings as configured for the first node. You do not need to specify the path to any disks during an Add Node installation.
[*]Complete the installation on the additional node.
[/list]
[img]http://www.mssqltips.com/tipimages2/2817_localtempdb15.jpg[/img]
[b] SQL Server Cluster Failover Validation[/b]

You have now completed installing SQL Server 2012 on at least 2 nodes to form a cluster. The next step would be to verify cluster failover between nodes.
[list]
[*]On the first node Open the Failover Cluster Manager.
[*]Select [b]Move this service or application to a different node[/b] on the SQL Server group as shown below.


[img]http://www.mssqltips.com/tipimages2/2817_localtempdb7.jpg[/img]
[*]It is possible that the SQL Server resource and the SQL Agent resource fail to come up on the second cluster node.


[img]http://www.mssqltips.com/tipimages2/2817_localtempdb8.jpg[/img]
[*]Open the system Event Viewer to check for any messages related to the resource not coming online.
[*]You will see Error Events 5123 and 17204 in the Event Viewer Application Log.


[img]http://www.mssqltips.com/tipimages2/2817_localtempdb9.jpg[/img]
[*]These errors are related to the local path for TempDB not being created on the additional cluster node.


[img]http://www.mssqltips.com/tipimages2/2817_localtempdb10.jpg[/img]
[*]Create the same exact path for TempDB on the additional node.

[img]http://www.mssqltips.com/tipimages2/2817_localtempdb11.jpg[/img]
[*]Now attempt to move the SQL Server group to the second node again. If the same local path is available the TempDB files will be created. SQL Server will automatically apply the proper permissions to the directory.

[img]http://www.mssqltips.com/tipimages2/2817_localtempdb12.jpg[/img]
The cluster should now fail over between all nodes while utilizing local disk for TempDB on each node.


[img]http://www.mssqltips.com/tipimages2/2817_localtempdb13.jpg[/img]
[/list]
[/quote]

Love this clustering

[9Pardhu]

[quote name='Kaarthikeya' timestamp='1356121681' post='1302996849']
evaraina SQL nundi batch file ela execute cheyyalo cheppandi..other than xp_cmdshell
[/quote]


google lo chala vastuai other than xp_cmdshell