SQL Journey - All Comments

re: SQL 2008/2008 R2/2012 setup disappears/fails when installing Setup Support files

HarshDeep_Singh — Tue, 14 May 2013 12:13:59 GMT

Thank you Lexa. Glad to know it helped.

re: SQL 2008/2008 R2/2012 setup disappears/fails when installing Setup Support files

Lexa — Tue, 14 May 2013 12:03:06 GMT

Спасибо дорогой! =) Дай Бог тебе здоровья!

re: An in-depth look at Ghost Records in SQL Server

HarshDeep_Singh — Sun, 12 May 2013 15:25:31 GMT

Hi Eric,

Let's take the example I specified in the blog. If you delete the 30 record from a heap table, the records will be deleted physically (or rolled back completely), and only then will the delete operation return. So there is no possibility of an insert of record value 30 conflicting with the delete operation down the line. Also, the delete operation against the heap uses heap level locks, since we do not have a clustered index to allow us to take key range locks. Hope this helps.

Please feel free to drop me an email if you would like to discuss this further.

re: An in-depth look at SQL Server Memory–Part 3

HarshDeep_Singh — Sun, 12 May 2013 15:23:30 GMT

Thanks Nishant. :)

re: An in-depth look at SQL Server Memory–Part 3

NISHANT — Sun, 12 May 2013 13:13:46 GMT

GOOD WORK

re: An in-depth look at Ghost Records in SQL Server

ERIC — Fri, 10 May 2013 10:37:56 GMT

THANK YOU Harsh.

"insert can conflict with a delete operation "? do you refer to the unique constraint ?can you kind of helping to explain it more details?

re: An in-depth look at Ghost Records in SQL Server

HarshDeep_Singh — Thu, 09 May 2013 07:03:30 GMT

Hi Eric,

Thanks for showing interest in the blog. A few reasons:

1. We do not use keyrange locks in heaps

2. There is no way a new insert can conflict with a delete operation that is under rollback, since we anyway use heap level locks when performing updates/inserts/deletes on heaps

The only case where heaps have ghost records is when we use versioning (snapshot isolation).

Hope this helps.

Regards,

Harsh

re: SQL 2008/2008 R2/2012 setup disappears/fails when installing Setup Support files

HarshDeep_Singh — Sun, 05 May 2013 07:42:15 GMT

Hi Russweb,

Thanks for showing interest in the blog. I would like to point out 2 things here:

1. The mentioned registry entries "should" exist. This is why I have requested to save the text in a .reg file and double click to merge those entries.

2. The error code that this blog is for is 0x80070003, which is different from the one you're getting. So, even though I feel the steps outlined above are worth a shot, it's quite possible that you're facing a different issue altogether.

Kindly email me the complete setup logs if you would like to take this further.

Hope this helps. Thanks.

re: SQL 2008/2008 R2/2012 setup disappears/fails when installing Setup Support files

Russweb — Fri, 03 May 2013 19:05:26 GMT

From Log:

05/03/2013 12:40:56.837 Attempting to launch process C:\Installers\SQL 2008 R2\x64\setup100.exe

05/03/2013 12:41:25.603 Process returned exit code: 0x84BC0057

05/03/2013 12:41:25.603 Workflow COMPONENTUPDATE returned exit code: 0x84BC0057

05/03/2013 12:41:25.603 Attempting to determine security.config file path

05/03/2013 12:41:25.603 Attempting to load .Net security policy file

05/03/2013 12:41:25.603 Attempting to remove .Net security code group node

re: SQL 2008/2008 R2/2012 setup disappears/fails when installing Setup Support files

Russweb — Fri, 03 May 2013 19:02:09 GMT

The mentioned registry entries did not exist.

So I moved on to copy the files to the spots indicated. Still have same failure.