384 reputation
210
bio website connectsql.blogspot.com
location
age
visits member for 2 years, 3 months
seen 54 mins ago

1h
answered Does a database backup reduce size/increase free space of the log file?
1h
answered Which one is better performance and (approach): store as rows or as a varchar column
3h
comment Does a database backup reduce size/increase free space of the log file?
Full database backup will not reduce log file size, it just create copy of tail log from log file but don't reduce log file size. If you want reduce size you must execute DBCC SHRINKDATABASE (YouDatabaseName, TRUNCATEONLY);
1d
revised SQL Server Replication (Login failed for user 'NT Service\SQLAgent$SQL2014')
error message should be separate in correct format
1d
comment SQL database rejoined to new SQL Server 2008 R2. Users are still unable to connect
msdn.microsoft.com/en-us/library/ms188670.aspx
1d
comment SQL Server Replication (Login failed for user 'NT Service\SQLAgent$SQL2014')
Make sure that 'NT Service\SQLAgent$SQL2014' is assigned sysadmin fixed role, it not assign it using sp_addsrvrolemember
1d
comment SQL database rejoined to new SQL Server 2008 R2. Users are still unable to connect
You are using Windows Authentication only or mixed mode too ?
1d
comment SQL Server Replication (Login failed for user 'NT Service\SQLAgent$SQL2014')
How many instances you have installed on your machine ?
1d
suggested suggested edit on SQL Server Replication (Login failed for user 'NT Service\SQLAgent$SQL2014')
2d
comment Explicit transactions for each DML query are necessary or not?
For implicit transactions where you don't start your script with Start Transaction and ends with Commit or Rollback, MySQL by default consider Start Transaction at start and Commit at the end (implicit transaction).
2d
awarded  Explainer
2d
revised Explicit transactions for each DML query are necessary or not?
question heading is too long, rather it should be explained in detail portion
2d
suggested suggested edit on Explicit transactions for each DML query are necessary or not?
2d
answered Explicit transactions for each DML query are necessary or not?
2d
comment Large Data Long Query A Lot of Joins horibble performance
You are right, but you must keep in mind that wildcard '%' on both side will lead to index scan and in result poor performance. Normally first name is a single complete word so using wildcard make no sense but still you know your business rules better.
2d
comment Large Data Long Query A Lot of Joins horibble performance
@Coninglnsane that i was trying to prove. Actual problem in your query is LIKE operator. Optimizer are not good to handle LIKE OPERATOR as cost estimation is not simple with this operator, resultantly poor execution plan is selected to execute query. If %term% is the only criteria then you can create extra column in person, a computed column with rule that if firstname like %term% then bit value 1 else 0. or like that.
2d
comment Large Data Long Query A Lot of Joins horibble performance
If you have proper indexes on columns used in JOIN clause then make sure how much time it takes to execute if you remove LIKE operators ? And why these joins JOIN person c ON a.family_id = c.id JOIN person d ON a.family_id = d.id JOIN person e ON a.family_id = e.id
2d
revised dynamic table can't be accessed by the users
some spelling mistakes
2d
revised How to limit results using join in SQL in php
SQL code need to be in correct format
2d
revised Additional space required for INDEX REORGANIZE
added 100 characters in body