|
|
-
Sergejack Learned 1 Years ago through Just Learned | 1 Point
While installing a windows service I wrote this command in my installation script (not using the installutil.exe) and used a service user account.
SC.EXE create MyService
binPath= "%CD%\MyService.exe"
start= auto
obj= "domain\Myserviceuse...
|
-
Sergejack Liked 1 Years ago through Just Learned | 1 Point
While installing a windows service I wrote this command in my installation script (not using the installutil.exe) and used a service user account.
SC.EXE create MyService
binPath= "%CD%\MyService.exe"
start= auto
obj= "domain\Myserviceuse...
|
-
Sergejack Liked 1 Years ago through Just Learned | 1 Point
While installing a windows service I wrote this command in my installation script (not using the installutil.exe) and used a service user account.
SC.EXE create MyService
binPath= "%CD%\MyService.exe"
start= auto
obj= "domain\Myserviceuse...
|
-
Sergejack Liked 1 Years ago through Just Learned | 1 Point
When using INSERTs on large tables (> 1 millon rows), the SCOPE_IDENTITY() or @@identity functions sometimes return wrong results.
This is NOT supposed to be fixed in SQL Server versions older than 2012!
...
|
-
Sergejack Liked 1 Years ago through Just Learned | 1 Point
When using INSERTs on large tables (> 1 millon rows), the SCOPE_IDENTITY() or @@identity functions sometimes return wrong results.
(*This was NOT supposed to be fixed in SQL Server versions older than 2012!*)
**Update:** It seems the problem has be...
|
-
Sergejack Learned 1 Years ago through Just Learned | 1 Point
When using INSERTs on large tables (> 1 millon rows), the SCOPE_IDENTITY() or @@identity functions sometimes return wrong results.
This is NOT supposed to be fixed in SQL Server versions older than 2012!
...
|
-
Sergejack Learned 1 Years ago through Just Learned | 1 Point
When using INSERTs on large tables (> 1 millon rows), the SCOPE_IDENTITY() or @@identity functions sometimes return wrong results.
(*This was NOT supposed to be fixed in SQL Server versions older than 2012!*)
**Update:** It seems the problem has be...
|
-
Sergejack Commented 1 Years ago through Just Learned | 1 Point
NEWID() is evaluated for each resulting rows while RAND() is evaluated for the whole resultset.
It's really important to know NEWID is evaluated afterward in order to understand what happens when you try this :
SELECT
*
FROM (VALUES...
|
-
Sergejack Commented 1 Years ago through Just Learned | 1 Point
NEWID() is evaluated for each resulting rows while RAND() is evaluated for the whole resultset.
It's really important to know NEWID is evaluated afterward in order to understand what happens when you try this :
SELECT
*
FROM (VALUES...
|
-
Sergejack knew 1 Years ago through Just Learned | 1 Point
Sometimes it happens that we need random row (or set of randoms rows) from table.
Itzik Ben-Gan shows us, in one of his book, the efficient way to do this:
SELECT TOP(1) FROM someTable ORDER BY NEWID()
Changing the val...
|