Viewing 15 posts - 3,751 through 3,765 (of 59,098 total)
It likely has to do with which login on the target of the linked server was used and what the privs are on the target server for that login.
For example,...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 26, 2022 at 9:54 pm
To be sure, my laugh wasn't about your bit of misfortune. I was laughing because it appears to be yet another limitation of Azure. 😀
Actually, it works in...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 26, 2022 at 1:56 pm
I wouldn't even dream of doing this simple thing in PowerShell. I also can't help you if you want it done in PowerShell.
If you want it done in T-SQL,...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 26, 2022 at 1:39 am
If you want referential integrity between all those tables and 1 notes table, it will need to be done by a trigger instead of DRI through FKs.
Much like temporal tables,...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 25, 2022 at 9:56 pm
Hey Michael good point, which now putting it all together, i think I might see a problem here... and the keyword is trigger, which from table 1 on database...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 25, 2022 at 9:08 pm
If they're still too incompetent to do it, hopefully they (1) realize that and get help (2) you realize that and get rid of them if they just can't...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 25, 2022 at 9:05 pm
Since you're only checking for an hour range, you can use BETWEEN. It's just as accurate and easier to code and read.
I agree that it's real tempting to use...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 25, 2022 at 7:28 pm
I have to ask... why are you trying to use PowerShell to do this? And you have the comment "# Loop through all tables and export a CSV of the...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 25, 2022 at 6:59 pm
Shifting gears a bit... the following message started showing up on my machine some time ago (seems like at least a week) on every post thread and ONLY...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 25, 2022 at 4:30 pm
below is to get business hours data
SELECT * FROM #TEMP WHERE CAST(LOADDATE AS TIME) BETWEEN '9:00:00' AND '17:59:59'
Thanks for your help
My recommendation is to get out of the habit...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 25, 2022 at 4:25 pm
To be sure, my laugh wasn't about your bit of misfortune. I was laughing because it appears to be yet another limitation of Azure. 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
March 25, 2022 at 4:02 pm
It sounds like you have to rebuild the "proxy" account to make it work.
And using xp_CmdShell isn't a "terrible security practice". Giving non-DBA users the privs to run it directly...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 25, 2022 at 2:02 pm
BWAAA-HAAA-HAAA!!! (Sorry... couldn't help the laugh).
--Jeff Moden
Change is inevitable... Change for the better is not.
March 25, 2022 at 1:55 pm
Congratulations on the retirement. I've just about given up on SO. Discussions are discouraged... unless you happen to be a moderator. 🙁
--Jeff Moden
Change is inevitable... Change for the better is not.
March 25, 2022 at 1:46 pm
Shifting gears a bit... the following message started showing up on my machine some time ago (seems like at least a week) on every post thread and ONLY for this...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 25, 2022 at 10:26 am
Viewing 15 posts - 3,751 through 3,765 (of 59,098 total)