Viewing 15 posts - 61 through 75 (of 88 total)
if only 10 is selected then also it should be correct answer
February 5, 2015 at 1:27 am
Is there any job running on the database performing DML operations , that might be the reason.
February 4, 2015 at 10:54 pm
You can check the owner of the jobs created after replication setup. Job for replication snapshot, log reader agent, distribution
February 4, 2015 at 8:55 pm
Thank you. Really helpful script
February 3, 2015 at 4:23 am
Can you again check the xml whether it has string for any records
February 3, 2015 at 4:20 am
I never faced this error. I tried changing password of sa and log in. Didn't logged any error
February 2, 2015 at 10:38 pm
Performance of both will be same. I tested both queries on my test database. I got same execution plan for both ISNULL and Case statement
February 1, 2015 at 10:00 pm
Performance of both will be same. I tested both queries on my test database. I got same execution plan for both ISNULL and Case statement
February 1, 2015 at 10:00 pm
It is [Databasename].[Schema].[ObjectName]. When [Databasename]..[ObjectName] is used, SQL Server wil consider default schema
January 30, 2015 at 1:38 am
I executed the script on SQL Server 2008. It returned "10 row(s) affected", the csv file created but no records in the file
January 29, 2015 at 10:59 pm
This might help
https://cmatskas.com/fixing-error-cannot-generate-sspi-context-after-changing-sql-service-account/
January 28, 2015 at 10:17 pm
You need to use any aggregate function on columns col2, col3 as these are not part of group by clause.
January 28, 2015 at 10:15 pm
Is there any other trigger created on table ? or unique constraint created on table you are updating?
January 28, 2015 at 10:09 pm
Viewing 15 posts - 61 through 75 (of 88 total)