Disaster Recovery plan is our business continuity plan. Disaster recovery is a process that we can use to help recover information systems and data, if a disaster occurs. The planning includes the selection of a strategy to help recover valuable data. The selection of the appropriate disaster recovery strategy depends on your business requirements.

Suppose we have a database system storing financial application data, an organization whole business is running on some applications and data is stored in database. Lets our database system machine is placed in the same organization, now if tomorrow database machine crashed then???, all our data gone, what about that organization business records, is that organization will be able to continue business?

So if I had solid Disaster Recovery plan for our organization data then your organization business will not stop and it can continue, for the organization only it will be a matter of one system crash. So in disaster recovery what you do is configure some backup mechanism on some other machine to keep the same piece of information what you have on your current database machine. So if our current database machine dead then you can recover your all data from backup machine. In our support plan we are always come with a solid DR plan as per the client requirement.

Key Questions to Customer:

The first step in testing your disaster recovery plan is to ask customer some poignant questions and respond in simple terms, maybe even 1 word answers.

SLA – What is your Service Level Agreement (SLA) with the business with customers?

Cost – What is the tangible cost of downtime for your users, application, business, etc?

Prevention – What type of disaster are we trying to prevent?

Recovery – What type of disaster are we trying to recover from?

Time – How much time and money do have to spend on building, testing and maintaining the disaster recovery plan on a daily, weekly, monthly or quarterly basis?

Responsibility – What are your disaster recovery responsibilities and why do you have those responsibilities?

Plan –Documented disaster recovery plan?

Testing – Have you tested the disaster recovery plan?

The selection of the appropriate disaster recovery strategy depends on customer business requirements.

Disaster recovery in SQL Server

Microsoft SQL Server database system provides multiple ways to configure disaster recovery.

• Failover clustering
• Database Mirroring
• Database Replication
• Log shipping
• Timely database Backup strategies

Failover clustering

Microsoft SQL Server failover clustering is designed to failover automatically if a hardware failure or a software failure occurs. You can use SQL Server failover clustering to create a failover cluster for a single instance of SQL Server 2000 or for multiple instances of SQL Server 2000. Failover clustering allows a database system to automatically switch the processing of an instance of SQL Server from a failed server to a working server. Therefore, failover clustering is helpful if an operating system failure occurs or if you perform a planned upgrade of the database system resources. Also, failover clustering increases server availability with no downtime.

Because failover clustering is designed for high server availability with almost no server downtime, the clustered nodes should be geographically close to each other. Failover clustering may not be useful if a disk array failure occurs.

Advantage

• You have high server availability. Failover clustering automatically occurs if the primary server fails.

Disadvantages

• You incur a greater expense. The maintenance of two servers is two times the cost of maintaining a single server. Because you have to maintain two servers at the same time, it is more expensive to install and maintain clustered nodes.
• Servers should be in the same location. If the branches of the organization are across the globe and the Active/Active clusters must be implemented in the branches, the networking and the storage infrastructure that you have to use is very different from a standard quorum device server cluster. Therefore, although it is possible, it is best not to use geographically distant servers.
• You have no protection against a disk array failure.
• Failover clustering does not allow you to create failover clusters at the database level or at the database object level, such as the table level.

Database mirroring

Database mirroring is a primarily software solution for increasing database availability. We can only implement mirroring on a per-database basis. Mirroring can only works with databases that use the full recovery model. The simple and bulk-logged recovery models do not support database mirroring. Therefore, all bulk operations are always fully logged. Database mirroring works with any supported database compatibility level.

Advantages

• Database mirroring increases data protection.
• Database mirroring increases availability of a database.
• Database mirroring improves the availability of the production database during upgrades.

Disadvantages

• The mirror database should be identical to the principal database. For example, all objects, logins, and permissions should be identical.
• Database mirroring involves the transfer of information from one computer to another computer over a network. Therefore, the security of the information that SQL Server transfers is very important.

Peer-to-peer transactional replication

Peer-to-peer transactional replication is designed for applications that might read or might modify the data in any database that participates in replication. Additionally, if any servers that host the databases are unavailable, you can modify the application to route traffic to the remaining servers. The remaining servers contain identical copies of the data.

Advantages

• Read performance is improved because you can spread activity across all nodes.
• Aggregate update performances, inserts performance, and delete performance for the topology resembles the performance of a single node because all changes are propagated to all nodes.

Disadvantages

• Peer-to-peer replication is available only in SQL Server 2005 and 2008  Enterprise Edition.
• All participating databases must contain identical schemas and data.
• We recommend that each node use its own distribution database. This configuration eliminates the potential for SQL Server 2005 to have a single point of failure.
• We cannot include tables and other objects in multiple peer-to-peer publications within a single publication database.
• We must have a publication enabled for peer-to-peer replication before you create any subscriptions.
• We must initialize subscriptions by using a backup or by setting the value of the subscription synchronization type to replication support only.
• Peer-to-peer transactional replication does not provide conflict detection or conflict resolution.
• We recommend that you do not use identity columns.

Log shipping

Log shipping uses a standby server that is not used during regular operations. A standby server is useful to help recover data if a disaster occurs. We  can only use log shipping at the database level. We cannot use it at the instance level.

When a standby server is restoring transaction logs, the database is in exclusive mode and it is unusable. For Applications such as decision support servers that require continuous processing on a database server, log shipping is not an appropriate option.

The latency on the standby server is based on how frequently the transaction log backups are taken at the primary server and then applied at the standby server. If the primary server fails, you may lose the changes that were made by the transactions that occurred after your most recent transaction log backup.

For example, if transaction log backups are taken every 10 minutes, transactions during the most recent 10 minutes may be lost. This does not necessarily mean that the data updates that are made to the primary server during the latency period will be lost. Typically, new updates in the primary transaction log can be recovered and applied at the warm standby server with only a small delay in switching from the primary server to the standby server. The main purpose of log shipping is to maintain a warm standby server. If maintaining a warm standby server is your main objective, log shipping is likely to be more appropriate than the other solutions that this article discusses.

Advantages and disadvantages of using log shipping

Advantages

• We can recover all database activities. The recovery includes any objects that were created such as tables and views. It also includes security changes such as the new users who were created and any permission changes.
• We can restore the database faster. The restoration of the database and the transaction log is based on low-level page formats. Therefore, log shipping speeds up the restoration process and results in the fast recovery of data.

Disadvantages

• The database is unusable during the restoration process because the database is in exclusive mode on the standby server.
• There is a lack of granularity. During the restoration process, all the changes in the primary server are applied at the standby server. You cannot use log shipping to apply changes to a few tables and to reject the remaining changes.
• There is no automatic failover of applications. When the primary server fails because of a disaster, the standby server does not failover automatically. Therefore, you must explicitly redirect the applications that connect to the primary server to the standby (failover) server.

Note If your main purpose is to maintain a warm standby server, Microsoft recommends that you use log shipping. The warm standby server reflects all the transactions that occur on the primary server. However, you cannot use the standby server when the primary server is available.

Timely Database Backup Strategies

If our disaster recovery plan we are planning for timely databases backup then all what we have to do is:

• Take backup of all database from the database server (you can schedule a job in sql server to do take backup of all databases)
• Copy all back up files to your file server or some other directory
• Need to write schedule daily/weekly backup plan in sql server
• Write ourr daily backup / weekly back up in disk and store the disk at some safe place

Conclusion

In this article we had discussed about disaster recovery and disaster recovery plan in sql server. There are many ways you can configure disaster recovery for your database, in sql server database we  can use Failover Clustering  Database Replication, Timely Backup Strategies, Log Shipping, and Database Mirroring.

By:  Rajib Kundu

Share   Posted in Microsoft SqlServer Administration | 1773No Comments »http%3A%2F%2Fwww.citagus.com%2Fcitagus%2Fblog%2Fdisaster-recovery-plan%2FDisaster+Recovery+Plan2012-04-05+10%3A37%3A22nishikantsharmahttp%3A%2F%2Fwww.citagus.com%2Fcitagus%2Fblog%2F%3Fp%3D1773

Many times we do customization in CRM using script on various events. If something goes wrong it is difficult to find out the issue with script.
Now with Internet Explorer 8.0 it’s easy to debug script. To debug the script please follow below steps.

1. On the page where script error is occurs press F12 (Developer Tools), which will open new window where you can test the script.

2.  On the script tab, to the right of the “Start Debugging” button, use the drop-down to locate your JScript library or simply check for the script in the script pane.

3.  Set the breakpoint at the required place and check the result in right pane.

4.  To stop debugging click on “Stop Debugging” button.

5.  If the script is on page load, you need to hit F5 or refresh the page to reload window.

By:  Pramod Vilas Zite

Share   Posted in Microsoft CRM | 1769No Comments »http%3A%2F%2Fwww.citagus.com%2Fcitagus%2Fblog%2Fdebugging-script-in-mscrm%2FDebugging+script+in+MSCRM2012-04-05+10%3A23%3A18nishikantsharmahttp%3A%2F%2Fwww.citagus.com%2Fcitagus%2Fblog%2F%3Fp%3D1769

In MSSQL Server database mirroring, two databases reside on different SQL Server instances, both with the same data. Primary server is referred as principal server while secondary server is referred as mirror.

We make changes in principal schema and transaction records are sent from principal to mirror and it only works with the database in full recovery mode.

Setting up database mirroring can impair database performance and because of this Microsoft recommends setting up database mirroring in non-production scenario first.

If you want to setup mirroring with automatic failover you would have to set a third server called witness server. The witness server monitors the state of primary and mirror server and does not contain any data from database. Each instance of database mirroring can have only one principal server and one mirror.

When a database mirroring session starts the log records stored in principal log disk of principal database are stored in a send queue and send to mirror server and mirror server then writes the log records to its disk. These log records are stored in redo queue. Starting with the oldest record, the mirror server handles the log records in sequence. This ensures that the mirror database is continuously rolling forward as the mirror server redoes the log.

It is also recommended that the principal and mirror servers have comparable hardware and similar performance profiles.

To establish a new database mirroring session the principal and mirror server must be running the same edition of SQL Server. This must be a standard or enterprise edition of SQL server version 2005 or later. If it has witness, it too must have MSSQL Server 2005 or later installed however the witness server can be standard, enterprise, workgroup or express.

Mirroring session can be setup as synchronous as well as a synchronous, depending upon the requirement and resources available. In case of highly safe mode it will be synchronous and for high performance mode it would be asynchronous

With high safety mode with automatic failover it is necessary to have a high quality network however network quality is not much of issue for high performance mode or high safety mode without automatic failover.

Basic steps of setting up a database mirroring are

1-      Create endpoints

2-      Create logins

3-      Setup the mirror database

4-      Establish the session

5-      Adding the witness if going with automatic failover

A database endpoint uses a unique TCP listener port for establishing the session and each database mirroring server its own mirroring endpoint.

Database mirroring endpoint doesn’t exist by default; you can query sys.database_mirroring_endpoints to look for existing endpoints.

Database mirroring endpoint can be created as follows.

Next step is creating login but if your server is already configured with AD and logins are configured we can skip this.

Now in order to create mirror database we first need the full backup of database and transactional log from principal server.

Now we need to restore database and log on the mirror server.

Next step for setup of mirroring partners as follows. Since I have both the instance of MSSQL Server running in the same server so server name will be the same for both the MSSQL server instances.

Database mirror monitor to monitor mirroring

By:  Deep Pandey

Share   Posted in Microsoft SqlServer Administration | 1652No Comments »http%3A%2F%2Fwww.citagus.com%2Fcitagus%2Fblog%2Fdatabase-mirroring%2FDatabase+mirroring2012-04-03+14%3A14%3A01nishikantsharmahttp%3A%2F%2Fwww.citagus.com%2Fcitagus%2Fblog%2F%3Fp%3D1652

In the previous blog, we learnt how to extract the data from Oracle Database to Qlikview to create reports. Now, here we are going to create Table and Chart using the Qlikview with the help of Extracted Data from Oracle Database.

1.  Click the “Create Table Box” icon on the tool bar to create Table Box.

2. Now, the new table box window opens as shown below.

3. In this window, type your own title. In this example, the title is “Employee Pay Details” .

4. Click   “Add All” button to all the available fields to add it to the Table box. You can also make necessary changes in the newly created table by exploring the sort, presentation, style, number, font, layout and caption tabs to make the table more presentable.

5. Now click Apply and Ok button to close the “New Table Box” Window. The table will be created and available in the Qlikview now.

6. Click and Drag the newly created table to one side of the Qlikview Window.

7.  Now, align the table name and column name. To do that, please right click on the table and select “Properties” button.

8. “Table Box Properties” Window opens. In the General Tab, you will see the title which is aligned left by default.

9. Place the Cursor in front of the title”Employee Pay Details” and continuously press the tab key to place it center.

10. Now click, the Presentation tab, you will see all the fields available in the table and its default alignment on the right hand side.

11. Select the “DEPARTMENT_NAME” field and use the radio button to mark “Center” for Liable, Text, Number.

12. Repeat the steps for all the other three fields Employee Name, Hire_date  and Salary and make the radio buttons on for “Center Alignment”.

Finally click  apply and ok to close the Table Box Properties. The table will look like the below screenshot after doing the alignments. You can decide your own alignments whichever is comfortable for good look and feel.

13. Make sure you need to save the Qlikview whenever you are doing changes. Save by clicking Ctrl + S. You may also save the document by clicking Fileà Save option.

CREATING CHART USING QLIKVIEW WITH ORACLE DATABASE AS SOURCE

So far we have create a one Qlikview object “Table Box” with the data derived from Oracle Database as source. Now we are going to create  a simple chart for the same data available within the Table.

1. To Create Chart, click the “Create Chart” icon on the toolbar.

You can also create Chart by right clicking on the empty area of the Qlikview selecting  New Sheet Object -> Chart.

2. The General Chart window opens .

3. Type the windows tile as “Visual Data of Employee Details”. Click the Chart type “Pie Chart” and select Fast Type Change as “Pie Chart”. Click Next.

4. Now choose the Dimensions, select Employee Name and click Add button. Choose second dimension as Salary and click add button. Click Next.

5. Expression Window will open, now click the Add button to add the expressions. Edit expression window will open.

6. In the Edit expression Window, click the Function tab and choose “Aggregation” as function category and “Avg”as function name. Click Paste.

7.Now, click the Field tab once after the function Avg is pasted.

8. Select “Salary” as field  and click Paste button.

9. Close the bracket to complete the expression and click ok button.

10. Click “Finish” button to create the simple pie chart for the available data. The Chart will be created as shown below.

Now we created two qlikview objects viz..Qlikview Table box and Qlikview Pie Chart. In order to make them presentable we have to segregate the newly created qlikview objects into a new sheet.

11. To create new sheet, click “Layout” and click “Add Sheet” option.

12. The new sheet will appear next to Main tab and it looks like in the screenshot below.

13. Now we need to give a suitable name to the Sheet1. To do that, right click anywhere on the empty area of Sheet1 and select “ properties”.

14. Sheet properties window will open.

15. Click  “ General” tab and rename the title from “Sheet1” to “ Table and Chart”.

Click Apply and Ok to close the   Sheet Properties Window.

16. Now click the “Main” tab to bring the Table box and Chart objects to “Table and Chart” sheet.

17. In the Main sheet, click and hold the “Employee Pay Details” table box and drag it to the new sheet “Table and Chart”. Now, the table box will disappear from the Main sheet and it will be available in the “Table and Chart” sheet.

18. Similarly click and drag the newly created Pie chart from the “Main Sheet” to the “Table and Chart” sheet. Now, you will see both the objects available on “Table and Chart” Sheet.

19. You can click and drag the edges of the Qlikview objects to resize it according to your needs.

20. Now, just click on the ‘IT’ field in the “Department Name” column of the table to see only the employees details (Employee name, salary and hire date ) of the employees in IT Department alone.

21. Correspondingly, you will see the visual data in the pie chart according to the Salary Range with unique colors for each individual.

22. Move the cursor over the Pie Chart on specific color and interstingly it will show the employee name, salary pointing the dimension.

From this document, we learnt…

• To create table box, a qlikview object with the extracted data from Oracle Database.
• To create Simple Chart with the available data.
• To create and edit the new sheet properties of the Qlikview object.
• To add sheet and rename the sheet.
• To migrate the Qlikview objects from one sheet to another sheet.

By:  Sivasankar K

Share   Posted in Qlikview | 1709No Comments »http%3A%2F%2Fwww.citagus.com%2Fcitagus%2Fblog%2Fcreating-table-and-chart-using-qlikview-with-the-extracted-data-from-oracle%2FCreating+Table+and+Chart+using+Qlikview+with+the+Extracted+Data+from+Oracle.2012-03-28+10%3A57%3A20nishikantsharmahttp%3A%2F%2Fwww.citagus.com%2Fcitagus%2Fblog%2F%3Fp%3D1709

Below are the steps to  extract data  to Qlikview from Oracle Database by establishing connection with Oracle database (as source)

EXTRACTING DATA FROM ORACLE DATABASE:

1. Click Start -> All Programs -> Qlikview -> Qlikview10.

2. Now, Qlikview start page opens.

3. Click the “Edit Source” button on the Qlikview Start Page as mentioned in the screenshot below.

4. After clicking the Edit Source button will opens the Edit Source Page opens.

5. Since we are going to retrieve the data from the Oracle Database, we need to make a connectivity between Oracle Database and Qlikview. To do this , select the Database as “ODBC” option and click the “Connect” button.

6. The “Connect to Data Source” Window opens. In this select the Schema from where you to retrieve data. I’ve already added OE as data source hence it is listing in the Data Sources.

NOTE:  If you have not added go head to add the data source by

• clicking Start -> Control Panel
• In Control Panel, double click “Administrative Tools” icon.
• Then double click “Data Sources(ODBC)” and click “System DSN” tab.
• It will show “Create New Data Source” window.
• Choose the Oracle Database and click Finish.
• Provide the Data Source Name and Service Name, Schema Name and Password.
• Click Ok to add the data source.

7. Select “OE” and provide Schema Name as User Id and enter the Password for the same schema and click ok to establish the connection.

8. Once the connection is successful, the script gets updated saying that ODBC connect to the Oracle Database.

9. Save the document as “Sample” without quotes, by clicking Fileà Save Entire Document.

10. Now, write your simple SQL to extract the required data in the “Edit Script” Window.

11. After writing the SQL, click “Reload” button to run the SQL from Qlikview to retrieve data from Oracle.

12. This will load the data as shown in the screenshot below.

13. Here you can select the columns that you want to use in the report. I need all these columns, so I clicked “Add All” buttons to add all the columns.

14. Now Click “Apply” and “OK” button to  bring the data in the report.

15. Now, re-arrange the data by clicking Layout button à Rearrange Sheet objects.

16. The Re-arranged data will look like below screenshot.

17. Clicking on the Department filed will highlighted as green and corresponding related columns will be highlighted as white fields with data. For E.g.: if I select IT department by clicking on it will show corresponding employee names working in IT Department and their Hire Date and Salary.

From the above steps, we learnt..

• To Open Qlikview and establish connection between Oracle Database and Qlikview.
• To Add Data source in Control Panel.
• To write SQL from Qlikview to load data.
• To re-arrange the Extracted Data in readable/presentable form.

By:  Sivasankar K

Share   Posted in Qlikview | 1691No Comments »http%3A%2F%2Fwww.citagus.com%2Fcitagus%2Fblog%2Festablising-connection-between-qlikview-and-oracle-to-extract-data%2FESTABLISING+CONNECTION+BETWEEN+QLIKVIEW+AND+ORACLE+TO+EXTRACT+DATA2012-03-27+14%3A53%3A53nishikantsharmahttp%3A%2F%2Fwww.citagus.com%2Fcitagus%2Fblog%2F%3Fp%3D1691

In Qlikview, using macro we can perform many automation functions using Macro. Below are the steps to export Qlikview objects (Table and Chart) to Microsoft Word as report to a predetermined location.

Step 1: Here is the Qlikview with two objects Table box and Chart which I’ve created already.

To Create Table and Chart objects in Qlikview please refer the previous post on our blog.

Step 2: Now, add a button named Export. Right click on the blank area of the Qlikview  and select New Sheet Object -> Button.

Step 3:  New Button Object Window Opens now.  Click on “General” Tab and type button name as “Export_to_ Microsoft _Word”.

Step 4: Then click on “Actions” tab.

Step 5: In the Action tab, click Add and select “External” and choose “Run Macro” button.

Step 6: Click Ok. Now click “Edit Module” button on the right side of “Button Properties” Window.

So far we have created the Button to export the Qlikview objects to Microsoft Word. In the following steps we are going to enable the button using Macro.

Step 7:  The below is the Macro Code to export the Qlikview object to Microsoft Word as a report to locate in a predetermined location.

‘‘defining Macro name
sub Export_to_Microsoft_Word
‘setting the object as Word and creating the application
set objWord = CreateObject(“Word.Application”)
objWord.visible = false
set objDoc=objWord.Documents.add
Const wdOrientLandscape = 1
‘setting the orientation for MS Word
objDoc.PageSetup.Orientation = wdOrientLandscape
‘instructing the Macro to copy the Table object(TB01)
ActiveDocument.GetSheetObject(“TB01″).CopyTableToClipboard true
objWord.Selection.Paste
‘Instructing the Macro to save the file in a particular location
objDoc.SaveAs “D:\EmpSalaryReport”
‘instructing the Macro to copy the Chart object(CHO1)
ActiveDocument.GetSheetObject(“CH01″).CopyBitmapToClipboard
objWord.Selection.Paste
objDoc.SaveAs “D:\EmpSalaryReport”
end sub

Step 8: After compiling the code, click the Check button to check if throws any error and debug it if so. If there are no errors it will show the status as “Ready”.

Step 9: Click Ok to close the “Edit Module” Window. And click “ok” to close the “Button Properties” Window.

Step 10. Now click the “Export_to_Microsoft_ Word” button.

Now you will see the Qlikview objects are exported to Microsoft Word as a report in the pre-determined location on the Macro code.

Step 11: Double click on the word file generated to see the report.

By: Sivasankar K

Share   Posted in Qlikview | 1676No Comments »http%3A%2F%2Fwww.citagus.com%2Fcitagus%2Fblog%2Fexporting-qlikview-objects-to-microsoft-word-to-a-pre-determined-location-%25e2%2580%2593-macro-enabled%2FEXPORTING+QLIKVIEW+OBJECTS++TO+MICROSOFT+WORD+%28TO+A+PRE-DETERMINED+LOCATION%29+%E2%80%93+MACRO+ENABLED2012-03-27+14%3A37%3A20nishikantsharmahttp%3A%2F%2Fwww.citagus.com%2Fcitagus%2Fblog%2F%3Fp%3D1676

1. Install windows power shell 1.0 or 2.0 on the centralized server.
2. By default the Set-ExecutionPolicy option is disabled
3. Need to change as Set-ExecutionPolicy unrestricted

• Run -> cmd-> type powershell -> Set-ExecutionPolicy unrestricted

ShellScript1 :

function main () {

GetServersFromFile

}

function GetServersFromFile () {

if ($verbose) {$VerbosePreference = “Continue”}

if ($debug) {$DebugPreference = “Continue”}

foreach ($svr in get-content “C:\1.txt”)

{

write-host $svr

GetDrivesInfoInsertScript $svr

}

}

#Function to get Drives Info Insert Script

function GetDrivesInfoInsertScript ($Server_Name)  {

write-host “Processing Server $Server_Name ”

trap [Exception]

{

$Err= $((get-date).toString() + “TRAPPED: ” + $_.Exception.Message + “– > $Server_Name “)

write-error  $Err

continue;

}

$Drives =Get-WmiObject win32_volume -ComputerName $Server_Name | where-object {$_.filesystem -match “ntfs”} |  select name,Label,Capacity,FreeSpace

foreach ($drive in $Drives) {

$name = $drive.name

$Label = $drive.Label

$FreeMB = ($drive.FreeSpace)/1MB

$TotalSpaceMB  = ($drive.Capacity)/1MB

$UsedSpaceMB = ($TotalSpaceMB – $FreeMB)

$PctFreeSpace = ( 100 * $FreeMB ) / $TotalSpaceMB

$PollDate =get-date

#write-host $Server_ID’,'$PollDate’,'$name’,'$Label’,'$TotalSpaceMB’,'$UsedSpaceMB’,'$FreeMB’, ‘$PctFreeSpace’

write-host $Server_ID $PollDate $name $Label $TotalSpaceMB $UsedSpaceMB $FreeMB $PctFreeSpace

}

}

Main

In the above script there is a path mentioned “C:\test\1.txt”)  go to path(any path) then edit the text file and put the full server names on separate line save and exit.

Example

Server1.twcable.com

Server2.twcable.com

Server2.twcable.com

How to execute shell script.

Set the path

Run  -> cmd -> type powershell ->  run the below command

$env:path = $env:path + “;c:\foldername”

Run the below command

. c:\scripts\shellscript1.ps1

The output will be in the same window where you are running the script.

By:  Umesh Madap

Share   Posted in Microsoft SqlServer Administration | 1673No Comments »http%3A%2F%2Fwww.citagus.com%2Fcitagus%2Fblog%2Fmonitor-free-space-from-mount-points-by-power-shell-script%2FMonitor+free+space+from+mount+points+by+power+shell+script.2012-03-26+11%3A46%3A48nishikantsharmahttp%3A%2F%2Fwww.citagus.com%2Fcitagus%2Fblog%2F%3Fp%3D1673

Content :

Assuming a valid master db recent backup, instead of rebuilding the master db using setup.exe follow the below steps so that master db is recovered much easier and faster, this works fine for both cluster and stand alone servers.

1)      Restore the master db backup in some other instance[SQL version should be same] but with different name (for ex: DB NAME: master_prod )while restoration make sure that the db file names are renamed to other than the default file names of the master DB,your file names may look this after changing the file names during restoration.

master_prod.mdf

mastlog_prod.ldf

2)      Now bring the db offline with below command

Use Master

Alter database master_prod set status offline

3)      Copy the master_prod.mdf and mastlog_prod.ldf files to the server path where the master db is corrupted and rename them to master.mdf and mastlog.ldf respectively(assuming existing master files are deleted or moved to some other path )

4)      Now start the SQL Services.

5)      Done, now the SQL service should start without any issues…Hope this helps…

By:  Mahesh Kumar P

Share   Posted in Microsoft SqlServer Administration | 1671No Comments »http%3A%2F%2Fwww.citagus.com%2Fcitagus%2Fblog%2Fmaster-database-corrupted-in-sql-server-2005-how-to-bring-back-easily-and-quickly%2FMaster+Database+corrupted+in+SQL+Server+2005+-+How+to+bring+back+easily+and+quickly%3F2012-03-26+11%3A43%3A07nishikantsharmahttp%3A%2F%2Fwww.citagus.com%2Fcitagus%2Fblog%2F%3Fp%3D1671

1. Install Silverlight 4 developer runtime in SharePoint Server machine.
2. Open the SharePoint Site, go to any document library and Add Document

3.  Click Browse and upload .Xap file of your Silverlight application. Click Ok

4.  Right Click on the document and Select properties

5.  Copy the Address (URL)

6.  Go to Site Actions and click New Page

7.  Give Page name as Drawing Demo and click Create

8.  Select Web Part under Insert tab

9. Choose Silverlight Web Part under Media and Content Category. Click Add

10.  Paste the Address(URL) of the Silverlight .Xap file. Click Ok

11.  Click Save & Close under Page tab

12.  Increase the width and height of this webpart as per your Silverlight application

13.  Click Annotation button at the bottom of the Silverlight Web Part to see the drawing tools panel

14.  Now select any tool and draw inside the Silverlight Webpart

By:  Vasanth M

Share   Posted in Sharepoint | 1654No Comments »http%3A%2F%2Fwww.citagus.com%2Fcitagus%2Fblog%2Fintegrating-silverlight-4-with-sharepoint-2010%2FIntegrating+Silverlight+4+with+SharePoint+20102012-03-26+11%3A39%3A52nishikantsharmahttp%3A%2F%2Fwww.citagus.com%2Fcitagus%2Fblog%2F%3Fp%3D1654

By using IBM Cognos mobile we can explore, access and analyze the reports where ever you are.

You can access the reports same way as you do with IBM Cognos BI.

Cognos mobile is more secure and reliable.

Cognos Mobile supports the following mobile technologies:

• iPhone
• iPad
• BlackBerry smart phones and playBook
• Nokia devices using Symbian operating system
• Windows Mobile OS

First we need to install the Cognos mobile server then we can access the reports from mobiles.

The Cognos mobile portal will be as below

• Cognos Report on iPhone:

• Cognos Report on iPad:

• iPhone and iPad Simulator:

• By using iPhone simulator  we can look and feel the cognos reports .

• We can download the iPhone and iPad simulator from the below link

http://www.electricplum.com/dlsim.html

• Once download and istall the Simulator one can access the iPhone Simulator

iPhone Simulator

• By clicking the device in menu bar we can switch to iPad

iPad Simulator

• BlackBerry Simulators:

Using the below link we can download the Black Berry simulators

http://swdownloads.blackberry.com/Downloads/contactFormPreload.do?code=DC727151E5D55DDE1E950767CF861CA5&dl=217F7A69F9E22A4BC5815BBF3DF60A9D&check1=A

Cognos Report on BlackBerry

• The following links can be used to configuring Mobile to work with Blackberry servers.

http://publib.boulder.ibm.com/infocenter/cbi/v10r1m1/topic/com.ibm.swg.ba.cognos.ig_mob.10.1.1.3.doc/c_mig_feats_cmpts.html#mig_feats_cmpts
http://publib.boulder.ibm.com/infocenter/cbi/v10r1m1/topic/com.ibm.swg.ba.cognos.ig_mob.10.1.1.3.doc/c_id__0installingandconfiguringibmcognosmobile.html#id__0InstallingandConfiguringIBMCognosMobile

By:  Thejesh Kumar

Share   Posted in Cognos | 1642No Comments »http%3A%2F%2Fwww.citagus.com%2Fcitagus%2Fblog%2Fcognos-mobile%2FCognos+Mobile2012-03-26+11%3A18%3A19nishikantsharmahttp%3A%2F%2Fwww.citagus.com%2Fcitagus%2Fblog%2F%3Fp%3D1642