|
Property IsLocked is not available
|
|
04.09.2009 10:40:49
- Filed under :
SQL
|
|
|
Property IsLocked is not available for Login '[DBName]'. This property may not exist for this object, or may not be retrievable due to insufficient access rights. (Microsoft.SqlServer.Smo)
Solution 1 : Restart computer
Solution 2 :
I ran into the same issue today when I installed an instance of SQL 2005 using Windows Auth. mode. After the install I switched the server over to SQL and Windows Auth mode and ran into the 'sa' problem. I ran the following command and then could see the properties of 'sa' within management studio.
alter login sa
with password = 'yourpwd' unlock,
check_policy = off,
check_expiration = off
Keywords : Sql login, islocked, insufficient
|
with 0 comments
|
|
|
No buffer space available Fix
|
|
29.08.2009 12:08:04
- Filed under :
C#
|
Asp.net
|
Misc
|
SQL
|
|
|
Error : An operation on a socket could not be performed because the
system lacked sufficient buffer space or because a queue was full
xxxx.xxxx.xxxx:80
Solution 1 :
I think I've found a reason for it: My anti-virus scanner, NOD32
v2.51.12 x64, with enabled HTTP scanning. If the HTTP scanning on port
80,8080,3128 and "Auto Detect HTTP communication on other ports" is
enabled, both versions will crash. After I disabled the IMON (Internet
Monitor) and EMON (MS Outlook E-Mail Monitor) features in NOD32
everything seems to work fine.
Solution 2 :
Editting the registry is not for beginners, if you don't know what
you're doing I suggest you don't try this, basically it's use at your
own risk. Anytime you want to edit the registry it is a good idea to
back it up first..
If you are using Windows 95/98/Me follow these steps:
First
step is to launch the registry editor. To do this go to Start, Run and
type regedit. In the left pane navigate to
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\MSTCP once
there, look for an entry called MaxConnections. If it exists highlight
it by clicking it and then right click it and select modify. Increase
the value (recommended value is to double the current value).
If
the MaxConnections entry does not exist you must create it. To do this,
right click in the right pane and choose new from the menu and select
String Value. Give it the name MaxConnections. Then right click it and
select modify and enter a value of 800.
Restart your computer,
if all goes well then you fixed the problem, if not, revert the changes
by restoring the registry. (You may have to reboot to safe mode to do
this).
If you are running Windows NT/2000/XP follow these steps:
First step is to launch the registry editor. To do this go to Start,
Run and type regedit. In the left pane navigate to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
once there, you must create the entry TcpNumConnections. To do this,
right click in the right pane and choose new from the menu and select
DWORD Value. Give it the name TcpNumConnections. Then right click it
and select modify and enter a value of 800.
Restart your
computer, if all goes well then you fixed the problem, if not, revert
the changes by restoring the registry. (You may have to reboot to safe
mode to do this).
Consideration :
TIP 1 :
I have seen NOD32 cause WSAENOBUFS (10055) on many systems. They seem
to do something which lowers the resources available to networking
applications.
TIP 2 : Problem is caused by a recent windows patch.
If you remove patch KB948609 the client side deserialization will
except large datasets again.
TIP 3 : If an application performs many
network connections simultaneously or within a short window of time,
the application developer might need to increase this number and reduce
the TcpTimedWaitDelay value to avoid receiving a WSAENOBUFS (10055)
error: "An operation on a socket could not be performed because the
system lacked sufficient buffer space or because a queue was full."
(http://msdn.microsoft.com/en-us/library/ms819739.aspx)
Keywords : WSAENOBUFS, 10055
|
with 0 comments
|
|
|
EXCEPT and INTERSECT (Transact-SQL)
|
|
16.05.2009 12:25:57
- Filed under :
SQL
|
|
|
The INTERSECT keyword returns a combined result set that consists of all of the rows that exist in both result sets.
Suppose you want to find a list of employee numbers that includes:
People in department D11
People whose assignments include projects MA2112, MA2113, and AD3111
INTERSECT returns the all of the employee numbers that exist in both result sets. In other words, this query returns all of the people in department D11 who are also working on projects MA2112, MA2113, and AD3111.
To do this, specify:
SELECT EMPNO FROM CORPDATA.EMPLOYEE WHERE WORKDEPT = 'D11' INTERSECT SELECT EMPNO FROM CORPDATA.EMPPROJACT WHERE PROJNO = 'MA2112' OR PROJNO = 'MA2113' OR PROJNO = 'AD3111' ORDER BY EMPNO
EXCEPT returns any distinct values from the left query that are not also found on the right query.
Keywords : Intersect and Except in Sql Server
|
with 0 comments
|
|
|
SQL Function
|
|
07.02.2009 22:09:58
- Filed under :
SQL
|
|
|
CREATE FUNCTION Hesapla (@Fiyat int)
RETURNS int
AS
BEGIN
DECLARE @donenDeger int
SET @donenDeger = @Fiyat * 1.18
RETURN @donenDeger
END
-- to call
select dbo.Hesapla(30)
Keywords : Create sql function in MS SQL
|
with 0 comments
|
|
Previous
|
Next
Current Page: 1
|
|