Viewing 15 posts - 6,526 through 6,540 (of 59,072 total)
Other that creating a parameter table the job reads from, I don't know anyone else that has been able to do it either.
out of curiosity what did you...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 25, 2020 at 10:45 pm
If needed I can provide examples of the excel files.
This can be done but I need to have a look-see... Attaching a couple would be a big help.
Of course,...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 25, 2020 at 7:28 pm
Hi,
Thanks for the solution. It works as expected. Just noticed the main table has an extra space at the beginning of each 1st value. How do I change the...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 25, 2020 at 7:06 pm
Try this.
SELECT Original
,Cleaned = REPLACE(Original,';#',', ')
FROM #ReplaceCharacters
;
Ah, careful now... 😉 It doesn't produce what the OP wanted. Instead, it includes a leading comma on all...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 25, 2020 at 6:19 pm
But my actual goal is , if the record insert into the underlying table then same record will be insert into the other table.
But the trigger should be on...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 25, 2020 at 4:52 pm
Agreed. I said similar in this post from above...
I missed this.
The difference is that I did the split using an indexed view. This way the split only happens...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 25, 2020 at 12:26 am
I haven't done this myself. I've mostly been running PoSh interactively for administrative scripting items. All my Agent jobs are T-SQL based or they use some batch scripting.
I was...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 24, 2020 at 10:53 pm
I haven't done this myself. I've mostly been running PoSh interactively for administrative scripting items. All my Agent jobs are T-SQL based or they use some batch scripting.
I was...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 24, 2020 at 10:40 pm
Bad choice of clustered index.
It must be not on identity column but on [Date].
I'll have to say "It Depends". If most queries are based on the ID, then the...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 24, 2020 at 6:10 pm
Actually, the number of views against this table are a pretty good indication of how much this table is used. Since it is so heavily used, it may be that...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 24, 2020 at 2:02 pm
<i>Hi All,</i>
I understood there is a table to table SQL Server Table & Data Comparision Tools, but this is for the table in same format & structure.
I finding, but...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 24, 2020 at 1:45 pm
My question would be... "This is good but how could you do this from a job in SQL Server"?
That's a great question. I'll see if I can write...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 24, 2020 at 7:28 am
p,s, Just because I'm giving you an answer you don't want to hear or maybe don't understand the ramification of, you should look into what I've said because it's going...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 23, 2020 at 9:10 pm
My question still stands - does column content (some values vs. all nulls) matter when altering column type from INT to BIGINT?
My answer still stands... it won't bother your...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 23, 2020 at 9:07 pm
As I have said - old values no longer needed, this recommendation is not really applicable
Actually, if you go back and read, I'm talking about the mess you might...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 23, 2020 at 9:04 pm
Viewing 15 posts - 6,526 through 6,540 (of 59,072 total)