Warning
You will need the space this large table takes up and downtime.

August 30, 2018 at 3:55 pm

#2004084

In SQL Server 2008 Resource Governor was introduced. It allows you to control CPU, Physical IO and  Memory effectively throttling run away queries.
https://docs.microsoft.com/en-us/sql/relational-databases/resource-governor/resource-governor?view=sql-server-2017

As far as I know, and that ain't far, SQLDoc generates database documentation, not entity relationship diagrams (ERD). In SSMS you can generate an ERD. Right click the Database Diagrams...

Are you using:
BEGIN TRY
..
END TRY

August 29, 2018 at 11:57 am

#2003865

I wouldn't create the permanent table in tempdb. If you aren't granted permissions in the database your procedures are in, ask for the permanent table to be created for you...

Is this a one off, or will this be regularly scheduled load?
Try specifying just the comma delimiter in SSIS, load into a staging table and write a stored procedure...

If you have a version that supports table partitioning I would read up on that.

What has all this to do with applying unique indexes or constraints to enforce uniqueness in a table?

I would agree with you on that. ADODB is better for SQL Server objects. I would like it better if MS made use of .net framework

August 27, 2018 at 4:32 pm

#2003530

DAO for Access objects specifically is easier. To get the same functionality you would need both ADO and ADOX. So say I want to write a script to link every...

Since the biggest bottle neck (or narrowest I guess) for databases is I/O, for servers with adequate memory you will see an improvement for read especially as more data will...

DAO is still the object model of choice when working with Access objects. You can use both if you want to and I have and do. Certain things are much...

Msg 241, Level 16, State 1, Line 27
Conversion failed when converting date and/or time from character string.