sql nerchukundam randiii... Ms sql server technology discussions...

[kum5758]

performance Tuning koncham information please.

chala interviews lo asking

using temp tables

joins

indexes

query exexution plan check chesi --table cost entha padthandi--

other than this 3 what should be do

[sri_india]

1 hour ago, loveindia said:

what technology are you into man?

Manual testing , kotha batch SQL dhi start ayinapudu cheppu , mamalni DB check cheyali as part of testing ani sava goduthunadu maa lead 

[mtkr]

2 hours ago, mastercheif said:

Differences between MS SQL vs ANSI SQL ?

ANSI sql - relational database language 
T sql (MS SQL) - Added feature of SQL with set programming extensions like varaibles, error handling etc

[k2s]

39 minutes ago, mtkr said:

daddy endhi e qtchn all mixx fruit juice laaga undiii

i dont know man.. adi telusukovali e week task naku 

[mtkr]

performance tunng:

 

For  performance, the columns used in joins should be of the same data types. And if possible, they should be numeric data types rather than character types.

Avoid SQL Server functions in the WHERE clause for Performance
--- when functions are used in the WHERE clause this forces SQL Server to do a table scan or index scan for results instead index seek if there is index that can be used.  b/c the function value has to evaluate for each row of data to determine the match. 

Use queries with NOLOCK to over come blocking issues

create index on filtered columns if query returns large data
create index on aggregate column if they are used in aggregate functions.
create index on column if its used in order by clause
(if more inserts updates r deletes are done then indexing this decrease performance)

use join instead of correlated sub query

[SlMHAM]

44 minutes ago, SwamyRaRa said:

Perfect 

Thanks

[sri_india]

4 minutes ago, mtkr said:

performance tunng:

 

For  performance, the columns used in joins should be of the same data types. And if possible, they should be numeric data types rather than character types.

Avoid SQL Server functions in the WHERE clause for Performance
--- when functions are used in the WHERE clause this forces SQL Server to do a table scan or index scan for results instead index seek if there is index that can be used.  b/c the function value has to evaluate for each row of data to determine the match. 

Use queries with NOLOCK to over come blocking issues

create index on filtered columns if query returns large data
create index on aggregate column if they are used in aggregate functions.
create index on column if its used in order by clause
(if more inserts updates r deletes are done then indexing this decrease performance)

use join instead of correlated sub query

mahatma , meeru SQL guruvu mahatma

[kum5758]

3 minutes ago, sri_india said:

mahatma , meeru SQL guruvu mahatma

 

8 minutes ago, mtkr said:

performance tunng:

 

For  performance, the columns used in joins should be of the same data types. And if possible, they should be numeric data types rather than character types.

Avoid SQL Server functions in the WHERE clause for Performance
--- when functions are used in the WHERE clause this forces SQL Server to do a table scan or index scan for results instead index seek if there is index that can be used.  b/c the function value has to evaluate for each row of data to determine the match. 

Use queries with NOLOCK to over come blocking issues

create index on filtered columns if query returns large data
create index on aggregate column if they are used in aggregate functions.
create index on column if its used in order by clause
(if more inserts updates r deletes are done then indexing this decrease performance)

use join instead of correlated sub query

Thanks Bhayya.

using functions in where clause-- 

[sanbk]

Mee andariki recent ga telisina interview questions veyandii so it will be useful for all. Navi kinda vesaa

Temp Table vs Table variable differences

Max recursion possible in CTE

Nested transactions rollback 

NoLock ante enti em chesthadi how it is related to one of the isolation level

Explain columnstore index in detail 

Multiple tables meeda base chesukoni create chesina view ni update chesthe view emavuthadi

Select 1/0 execute chesthe em vasthadii (try this only after making a guess to yourself)

Performance tuning ki eh template use chesavu profiler loo 

Parameterized views ante entii 

Merge eh enduku vadutharu indivdiual insert update delete vadachu kada

Identity reset ela effect avuthadi table ni truncate or delete chesthee  inka unnayi will post.....

[SwamyRaRa]

5 minutes ago, sri_india said:

mahatma , meeru SQL guruvu mahatma

Vuu

[ARYA__]

K

[k2s]

11 minutes ago, mtkr said:

performance tunng:

 

For  performance, the columns used in joins should be of the same data types. And if possible, they should be numeric data types rather than character types.

Avoid SQL Server functions in the WHERE clause for Performance
--- when functions are used in the WHERE clause this forces SQL Server to do a table scan or index scan for results instead index seek if there is index that can be used.  b/c the function value has to evaluate for each row of data to determine the match. 

Use queries with NOLOCK to over come blocking issues

create index on filtered columns if query returns large data
create index on aggregate column if they are used in aggregate functions.
create index on column if its used in order by clause
(if more inserts updates r deletes are done then indexing this decrease performance)

use join instead of correlated sub query

qochens sir 

1) what is difference between Table/Index Scan vs Seek ? How SQL server evaluate(search row) in each case ? 

2) Create Index on filtered, aggregated col,  antey ela chestharu ? oka table lo index ni ela create chestharu ?

3) Join ki correlated sub query ki difference enti ? how does SQL server evaluate in each case ? why join is preferred ?

[k2s]

6 minutes ago, sanbk said:

Mee andariki recent ga telisina interview questions veyandii so it will be useful for all. Navi kinda vesaa

Temp Table vs Table variable differences

Max recursion possible in CTE

Nested transactions rollback 

NoLock ante enti em chesthadi how it is related to one of the isolation level

Explain columnstore index in detail 

Multiple tables meeda base chesukoni create chesina view ni update chesthe view emavuthadi

Select 1/0 execute chesthe em vasthadii (try this only after making a guess to yourself)

Performance tuning ki eh template use chesavu profiler loo 

Parameterized views ante entii 

Merge eh enduku vadutharu indivdiual insert update delete vadachu kada

Identity reset ela effect avuthadi table ni truncate or delete chesthee  inka unnayi will post.....

>How do you track the changes – insert/update/delete transactions on the table?

>if the table has no primary key and there are duplicate rows in the table, how would you retrieve the duplicate rows only?

>differences between rank and dense rank

> can we pass a table as an input to stored procedure? If yes how? If no why?

>Differences between clustered index and non-clustered index, when to use what?

>If there is a primary key column and a high selectivity column, which one would you prefer having a clustered index on?

>How many indexes can we have on a table?

>What is live lock and dead lock and no lock? What is it used for?

[SwamyRaRa]

1 minute ago, k2s said:

>How do you track the changes – insert/update/delete transactions on the table?

 

>if the table has no primary key and there are duplicate rows in the table, how would you retrieve the duplicate rows only?

 

>differences between rank and dense rank

 

> can we pass a table as an input to stored procedure? If yes how? If no why?

 

>Differences between clustered index and non-clustered index, when to use what?

 

>If there is a primary key column and a high selectivity column, which one would you prefer having a clustered index on?

 

>How many indexes can we have on a table?

 

>What is live lock and dead lock and no lock? What is it used for?

 

Ggggppppp gooogggllllee

[k2s]

Just now, SwamyRaRa said:

Ggggppppp gooogggllllee