Viewing 15 posts - 5,476 through 5,490 (of 59,089 total)
It's an amazing thing... I've been working with SQL Server since before SQL Server 7 came out and it just dawned on me that I've never tried to alter a...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 27, 2021 at 8:50 pm
In my sql server instance I renamed 'sa' account and disabled. I confirmed no sa account. I configured server side audit log and I can see some sa activities....
--Jeff Moden
Change is inevitable... Change for the better is not.
March 27, 2021 at 1:58 pm
Hi Pete,
This is interesting. I've never seen such a thing before. The reason for my question is I'm looking for something else that might be causing this problem for you. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 27, 2021 at 1:44 pm
Does 'tablename' in the errors you're getting match the tablename in the ALTER TABLE statement?
--Jeff Moden
Change is inevitable... Change for the better is not.
March 27, 2021 at 1:08 am
Hi
Accidental DBA here
We have an application that runs a select * on a table upon starting the application. There are 2.4 million rows in the table. Today it was...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 26, 2021 at 3:59 pm
BWAAAA-HAAAA-HAAA!!! Great title... and that's exactly what I'm doing! 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
March 26, 2021 at 7:51 am
HI Jeff,
I apricate your wanting to know I did not want to bother you with it, but I would like to get the SSIS to work. As I said...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 26, 2021 at 2:02 am
Crud... I went to hit QUOTE and, instead, hit REPORT by mistake. My apologies, Joe. I'll contact the webmaster and let them know.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 26, 2021 at 1:27 am
Your code fairs no better, Joe. Try running it and see the error.
Also, the columns in your CREATE TABLE statement don't match the columns in your SELECT statement.
And, your code...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 26, 2021 at 1:24 am
If you avoid "batching", it can be done with "minimal logging", which also nearly doubles the performance.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 25, 2021 at 8:47 pm
The title of this thread threw me... I thought we were trying to count the NULLs in a given column... which is different than the original script, as well.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 25, 2021 at 8:28 pm
Heh... you didn't try the code you posted. It's missing commas and the VALUES are not correct.
Be advised that the data you posted has nothing other than partid and serial...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 25, 2021 at 6:02 pm
I believe you'll find that and INSERT/SELECT from an OPENQUERY across a linked server will work with some pretty good performance.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 25, 2021 at 5:33 pm
Wouldn't it be easier just to take the difference between the count of a column that will never be NULL (like the PK column) and the column in question?
--Jeff Moden
Change is inevitable... Change for the better is not.
March 25, 2021 at 5:17 pm
The typical reason why there are typically no standards, particularly when it concerns databases and the related code, is because of the "code first" mentality that I've seen at oh...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 25, 2021 at 5:00 pm
Viewing 15 posts - 5,476 through 5,490 (of 59,089 total)