New answers tagged

0

I also could not find the plan until I come across this script, which finds the exact sql statement which originated that warning: Declare @ErrorLog Table (LogID int identity(1, 1) not null primary key, LogDate datetime null, ProcessInfo nvarchar(100) null, LogText nvarchar(4000) null); Insert Into @ErrorLog (LogDate, ProcessInfo, ...


0

I think this might be the answer and might help others with this problem. I had a test trigger on the table member CREATE TRIGGER `test` BEFORE UPDATE ON `member` FOR EACH ROW BEGIN DECLARE addr VARCHAR(100); DECLARE joint INT; SET @joint := is_joint_member(member.member_id); SET @addr = 'jgkjgkjg' ; CALL dummy2; ...


0

Please check this as well. Don't forget the .system hidden folder under /var/opt/mssql/. https://designprincipia.com/i-broke-mssql-server-on-linux


-1

You are facing the error Ambiguous column name… because the app is quering your database this way: SELECT [Name], [Salary], [Name], [Age] FROM TABLE1 A INNER JOIN TABLE2 B ON A.EmployeeID = B.EmployeeID As you can see there are two [Name] in the SELECT. You will resolve the issue by recreating the query this way: SELECT A.[Name], [Salary], B.[Name],...


2

As a DBA I've experienced more SPN issues than I'd care to imagine. For us, the SQL account we are allowed to use to install SQL Server do not have permissions to write the SPNs to Active Directory. So, SQL uses the NTLM authentication instead. And from there some SPN issues do rise to the surface. Having said all that, your question seems to arise ...


Top 50 recent answers are included