Windows 10: How to solve deadlock on SQLServer 2019 database with KEY and PAGE LOCK

I've a lot of deadlock on the same object of a SQLServer database. I'm trying to solve the issue. /****** Object: Index [PK_M6.TBL_PDC_T] ******/ ALTER TABLE [dbo].[M6.TBL_PDC_T] ADD CONSTRAINT [PK_M6.TBL_PDC_T] PRIMARY KEY CLUSTERED [PDCT_CENTATT] ASC, [PDCT_DATACONS] ASC, [PDCT_NUMPDC] ASC WITH PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, SORT_IN_TEMPDB = OFF, IGNORE_DUP_KEY = OFF, ONLINE = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON, OPTIMIZE_FOR_SEQUENTIAL_KEY = OFF ON [PRIMARY] GO -------------------------------------------------------------- /****** Object: Table [

:)

 

getting error while installing sqlserver 2012 standard edition 64 bit on window sqlserver 2019?

hi,

i am installing sqlserver 2012 standard edition 64 bit. its getting error like sqlserver browser services and database engine serices failed by following error.

The description for Event ID 1 from source SQLBrowser cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

 

Problem Activating Office 2019

You can save a few steps and do this

1. Go to this page: Microsoft 365
2. Log in with your Microsoft account
3. Enter your Office product key
4. Use the link given to download Office 2019
5. install Office 2019

I used this method for both of my copies of Office 2019

BTW, Microsoft Toolkit 2.71 says this:
Product Description: Office19_ProPlus2019MSDNR_Retail

 

Windows 10, SQLServer Express (2019), Excel 2016 import to SQLServer error Microsoft.ACE.OLEDB.12.0’ provider is not registered on the local machine

Apologies. This is likely not the right Category. Tips to fix this appreciated.

Environment:

Workstation: 16GB RAM. 500MB SSD

Windows 10 Pro (64-bit)

Microsoft Office 2010? 2016? (Home/Student?) Not sure how to tell exactly. Office reports the version as 18.2005.1191.0 ; Excel 2016

SQLServer 2019 (Express Edition) Just installed 2 weeks ago.

Not available on workstation (though some supporting libraries may be present, e.g. .NET framework 3.5 && 4.8 for Windows 10):

Visual Studio

C# compiler

etc.

Task:

Import a USA-state-government-supplied .csv (converted by me to an Excel spreadsheet) into SQLServer.

The spreadsheet ~20 columns and ~500K rows of data to be imported into 1 fairly simple SQLServer table. No stored procedures. No constraints, 1 Primary (Identity) Key.

Microsoft SQL Server Management Studio query windows limits an insert statement to 1,000 records/rows at a time. I did load 2,000 rows successfully. I do *not* want to break the Excel spreadsheet into 500 pieces to load the entire dataset. So, I thought
it would be best to use the database Import and Export Wizard to load the spreadsheet.

Error/roadblock (steps to reproduce):

Within Microsoft SQL Server Management Studio,

I select the database.

I select Tasks > Import Data ...

I follow the wizard's prompts, selecting Data Source -> Microsoft Excel; Excel file path (path to local spreadsheet file); Excel version -> Microsoft Excel 97-2003 (or Microsoft Excel 2007-2010 or Microsoft Excel 2013 or Excel 2016); First row has column
names; Next

An error is displayed:

TITLE: SQL Server Import and Export Wizard

The operation could not be completed.

ADDITIONAL INFORMATION:

The 'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine. (System.Data)

How can I fix this? TIA

Additional info:

ODBC Data Source Administrator (64-bit) Drivers tab has entries for

Microsoft Excel Driver 16.00.4513.1000 (ACEODBC.DLL)

SQL Server 10.00.18362.01 (SQLSVRV32.DLL)

ODBC Data Source Administrator (32-bit) Drivers tab has entries for

Microsoft Excel Driver 10.00.18362.01 (ODBCJT32.DLL)

SQL Server 10.00.18362.01 (SQLSVRV32.DLL)

Finally -

I saw this: datasavvy.me/2017/07/20/installing-the-microsoft-ace-oledb-12-0-provider-for-both-64-bit-and-32-bit-processing/

I tried the steps for Option B, but they did not change my outcome.