Unity : Satış fiyat kartlarının bitiş tarihini değiştirmek
UPDATE LG_208_PRCLIST SET ENDDATE='20101231' WHERE VALUE='20081231'
Unity : Faturası olmayan irsaliyeden F işaretini kaldırmak
Faturası olmayan irsaliyeden F işaretini kaldırmak için aşağıdaki query'ler kullanabilirsiniz.
1) Seçmek için;
SELECT * FROM LG_208_01_STFICHE WHERE BILLED=1 AND INVOICEREF NOT IN (SELECT LOGICALREF FROM LG_208_01_INVOICE)
2) Düzeltmek için;
UPDATE LG_208_01_STFICHE SET BILLED=0 WHERE BILLED=1 AND INVOICEREF NOT IN (SELECT LOGICALREF FROM LG_0208_01_INVOICE)
1) Seçmek için;
SELECT * FROM LG_208_01_STFICHE WHERE BILLED=1 AND INVOICEREF NOT IN (SELECT LOGICALREF FROM LG_208_01_INVOICE)
2) Düzeltmek için;
UPDATE LG_208_01_STFICHE SET BILLED=0 WHERE BILLED=1 AND INVOICEREF NOT IN (SELECT LOGICALREF FROM LG_0208_01_INVOICE)
Cannot resolve the collation conflict between "Latin1_General_CI_AI" and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation.
Problem:
select name from sysusers where name not in ( select name from master..syslogins )
Microsoft SQL Server 2005 - 9.00.1399.06 (X64)
Oct 14 2005 00:35:21
Copyright (c) 1988-2005 Microsoft Corporation
Standard Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 1)
(1 row(s) affected)
Msg 468, Level 16, State 9, Line 1
Cannot resolve the collation conflict between "Latin1_General_CI_AI" and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation.
Resolution:
This is because your master is in a different collation than your user database.
Try adding the COLLATE to your query.
select name from sysusers where name not in ( select name COLLATE Latin1_General_CI_AI from master..syslogins )
select name from sysusers where name not in ( select name from master..syslogins )
Microsoft SQL Server 2005 - 9.00.1399.06 (X64)
Oct 14 2005 00:35:21
Copyright (c) 1988-2005 Microsoft Corporation
Standard Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 1)
(1 row(s) affected)
Msg 468, Level 16, State 9, Line 1
Cannot resolve the collation conflict between "Latin1_General_CI_AI" and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation.
Resolution:
This is because your master is in a different collation than your user database.
Try adding the COLLATE to your query.
select name from sysusers where name not in ( select name COLLATE Latin1_General_CI_AI from master..syslogins )
SQL SERVER - Fix : Msg 15151, Level 16, State 1, Line 3 Cannot drop the login ‘test’, because it does not exist or you do not have permission
I got following error when I was trying to delete user ‘test’ with ‘SA’ login. I was little surprised but then I tried to delete with the windows authenticated systemadmin account. Once again I got the same error.
Msg 15151, Level 16, State 1, Line 3Cannot drop the login ‘test’, because it does not exist or you do not have permission.
The reason I was surprised that I was systemadmin and I should be allowed to delete the login. I am including the script which I used to delete the account here.
IF EXISTS (SELECT * FROM sys.server_principals WHERE name = N’Test’)
DROP LOGIN [Test]
Fix/Workaround/Solution:
I finally found out that error was misleading. I had another session open in SQL Server Management Studio with username ‘test’ and it was preventing me to drop the user. Once I closed that open session I was successfully able to delete the user using above script.
In Normal Case:Following error usually show up when user is logged in, which I did not get it.
Msg 15434, Level 16, State 1, Line 3
Could not drop login ‘test’ as the user is currently logged in.
However, when I tried to re-create scenario I got above error. I want to share this experience with users and want to know if they have ever faced this scenario.
Msg 15151, Level 16, State 1, Line 3Cannot drop the login ‘test’, because it does not exist or you do not have permission.
The reason I was surprised that I was systemadmin and I should be allowed to delete the login. I am including the script which I used to delete the account here.
IF EXISTS (SELECT * FROM sys.server_principals WHERE name = N’Test’)
DROP LOGIN [Test]
Fix/Workaround/Solution:
I finally found out that error was misleading. I had another session open in SQL Server Management Studio with username ‘test’ and it was preventing me to drop the user. Once I closed that open session I was successfully able to delete the user using above script.
In Normal Case:Following error usually show up when user is logged in, which I did not get it.
Msg 15434, Level 16, State 1, Line 3
Could not drop login ‘test’ as the user is currently logged in.
However, when I tried to re-create scenario I got above error. I want to share this experience with users and want to know if they have ever faced this scenario.
Kaydol:
Yorumlar (Atom)
BlackListIP control on Serenity platform (.NET Core)
In the Serenity platform, if you want to block IPs that belong to people you do not want to come from outside in the .net core web project,...
-
Logo Tiger programında kullanılan veritabanı tabloları aşağıdadır. 1. XXX olarak üç digit ile gösterilen bölüm firma numarasını belirtir....
-
Devexpress AspxGridView kolonlarında filtre türünü değiştirmek için grid üzerindeki ilgili kolonda Settings--> AutoFilterCondition = defa...
-
TABLO ADI AÇIKLAMA L_PERSONEL Çalışma Alanı Tanımları L_SYSLOG Kullanıcı Kaydı İzleme L_L...