Senior Database Engineer required for Thomson Reuters - Hyderabad / SQL Developer job at Thomson Reuters , Hyderabad

                                       

Designation: Senior Database Engineer

Job Location: Hyderabad
Notice Period: Must be ready to join at the earliest (Max 30 days)
Experience : 4 Years & above
CTC: As per Industry Standard
Job Type: Permanent

Hi,

We are pleased to inform you that, we have an urgent opening with our organization Thomson Reuters – Hyderabad.

Qualification:

 1. At least 4 years hands on experience in design and development of databases using Microsoft SQL Server 2005/2008
2. Expertise in designing and developing database solutions for enterprise transactional and reporting applications
4. Having knowledge in designing and modeling relational databases is an added advantage.

5. Strong ability to understand complex business logic and requirements to derive effective solutions
6. Extensive experience in T-SQL programming, developing, debugging and analyzing stored procedures with error handling, cursors, nested stored procedures, etc.
7.Expertise in creating/optimizing/debugging Stored Procedures, Functions, and Views
8.Good knowledge of data security best practices
9. Bachelor's degree in Computer Science or Math

10.  Dotnet frame work is an added advantage.

11. Must be able to debug/understand ADO dot net code.

12. Extensive knowledge in handling XML quires and dynamic quires

If you are interested in above opening then please help us with

updated profile along with below details ASAP:  

1) Total Exp:  
2) Relevant Exp:
3) Current CTC:
4) Expected CTC:
5) Notice Period:
6) Current Location:
7) are you ready to relocate (Hyderabad)? (Y/N):
8) Date of Birth:

Frequently Useful DBCC Commands In Sql Server DataBase

Microsoft SQL Server  provides a set of commands that will help you, called the DBCC commands. Originally that stood for Database Consistency Check commands, but they’ve been expanded since then to do a bit more. The DBCC commands are divided into four main categories: 

1. Status commands
2. Validation commands
3. Maintenance commands
4. Miscellaneous  commands.
 Let’s take a look at a few of the more common ones. 

How Import multiple images to SQL Server using SSIS

Sometimes we need to import thousands of images to SQL Server. This example shows how to import a list of images to SQL Server using SQL Server Integration Services.

Requirements

• SQL Server Enterprise or Standard (in this case I am using SQL Server 2008 R2, but it can work with SQL Server 2005 as well).
• SSIS installed (it is included in the SQL Server installer).

Demonstration

1. First of all, it is necessary to create a flat file named listImages.txt (or the name of your preference) with the paths of the images that you want to import to SQL Server such as the following:
   
   

Get the data from excel sheet to sql server

we can use the query according to our system requirement for example i have my system configuration like below:

os :windows 2003 server

sql server: 2005

ms excel: 2007

i select data from excel using the following configuration and query.

EXEC sp_configure 'show advanced options', 1;

GO

RECONFIGURE;

GO

EXEC sp_configure 'Ad Hoc Distributed Queries', 1;

GO

RECONFIGURE;

GO

SELECT * FROM

OPENROWSET

(

'MICROSOFT.ACE.OLEDB.12.0',

'EXCEL 12.0;DATABASE=D:example.XLSX;',

'SELECT * FROM [SHEET1$]'

)

What is Data Base Schema?

A database schema is a way to logically group objects such as tables, views, stored procedures etc. Think of a schema as a container of objects.

You can assign a user login permissions to a single schema so that the user can only access the objects they are authorized to access.

Schemas can be created and altered in a database, and users can be granted access to a schema. A schema can be owned by any user, and schema ownership is transferable.

Creating a Database Schema

1. Complete the details in the General tab for the new schema. In this example, the schema name is "person" and the schema owner is "Homer".
   
2. Add users to the schema as required and set their permissions:
   
3. Add any extended properties (via the Extended Properties tab)
4. Click OK.

Add a Table to the New Schema

Now that we have a new schema, we can add objects such as tables, views, and stored procedures to it. For example, we could transfer the table that we created in the earlier lesson to the new schema.
When we created that table (called "Individual"), it was created in the default database schema ("dbo"). We know this because it appears in our object browser as "dbo.Individual".
To transfer the "Individual" table to the person "schema":

1. In Object Explorer, right click on the table name and select "Design":
   
2. From Design view, press F4 to display the Properties window.
3. From the Properties window, change the schema to the desired schema:
   
4. Close Design View by right clicking the tab and selecting "Close":
   
5. Click "OK" when prompted to save

Your table has now been transferred to the "person" schema.

Confirm your Change

To confirm the change:

1. Refresh the Object Browser view:
   
2. You will now see that Object Browser displays the new schema for the table (person.Individual):
   

How To Use Linked Server

The Linked Servers option allows you to connect to another instance of SQL Server running on a different machine, perhaps remotely in a different city/country. This can be useful if you need to perform distributed queries (query a remote database). Setting up a linked server is quite straight forward in SSMS, all you need is details of the remote server, and the database that you need to query.

1. Navigate to Server Objects > Linked Servers
2. Right click on Linked Servers and select New Linked Server.... 

3. Complete the details for the linked server. In this example, Data source refers to the name of the SQL Server machine ("Barts_database_server"), Catalogue refers to the name of the database ("Barts_database"). You can also configure options in the other two tabs depending on your requirements.

Distributed Queries

Once you have configured your linked server, you will be able to run queries etc against it. When you run a query against a linked server, it is referred to as a distributed query.
When you execute a distributed query against a linked server, you must include a fully qualified, four-part table name for each data source to query. This four-part name should be in the form linked_server_name.catalog.schema.object_name.
Here's an example:

Barts_database_server.Barts_database.Person.Enemy

This example is based on the linked server example above. It assumes that the remote database has a schema called "Person" and a table called "Enemy".

Difference between sql server 2005 and sql server 2008

The features that have ms sql server 2008 over 2005 is following.here we are going to discuss some points

1.  SQL server 2008 has the ability to encrypt the entire database by using (TDE)).I.e  transparent data encryption. Where as in sql server 2005 we have cell-level encryption.
2. SQLserver 2008 provides Backup encryption and that will executed at backup time to prevent tampering.
3. External Key Management. Storing Keys separate from the data.
4. With SQL Server Audit, SQL Server 2008 introduces an important new feature that provides a true auditing solution for enterprise customers. While SQL Trace can be used to satisfy many auditing needs, SQL Server Audit offers a number of attractive advantages that may help DBAs more easily achieve their goals such as meeting regulatory compliance requirements. These include the ability to provide centralized storage of audit logs and integration with System Center, as well as noticeably better performance.
5. Data Compression. Fact Table size reduction and improved performance.
6. Collection of performance monitoring tools.With Performance Data Collector in SQL Server 2008, you can now store performance data from a number of SQL Servers in one central location. This data is collected by a collection set on each server and stored in a shareable management data warehouse (MDW). Reports can be generated from this data using the built-in reports or generating your own with reporting Services. Brad McGehee explains more.
7. installation improvements. Disk images and service pack uninstall options.
8. Dynamic Development. New ADO and Visual Studio options as well as Dot Net 3.
9. Entity Data Services. Line Of Business (LOB) framework and Entity Query Language (eSQL)
10. LINQ. Development query language for access multiple types of data such as SQL and XML.
11. Data Synchronizing. Development of frequently disconnected applications.
12. Large UDT(User-defined types). No size restriction on UDT(User-defined types).UDTs were restricted to a maximum size of 8 kilobytes. In SQL Server 2008, this restriction has been removed for UDTs that have a format of UserDefined
13.