Viewing 15 posts - 16 through 30 (of 6,353 total)
This one perhaps then?
October 1, 2024 at 10:47 am
Does this one work at all?
https://www.microsoft.com/en-us/download/details.aspx?id=103466
October 1, 2024 at 10:15 am
No, do not restore them from 2012 to 2019.
To transfer logins you can search for “sp_help_revlogin” this will generate you a script to move logins.
The best thing though is get...
October 1, 2024 at 6:57 am
Why do you manually want to do backups?
Why not let Azure manage the backups for you?
What is the use case / benefit your senior wants to get here?
October 1, 2024 at 5:58 am
Looks like ADS needs to authenticate to Git so it can push your changes to the remote repo
September 26, 2024 at 1:26 pm
You may need to play with some settings like lease timeout, health check timeout, connection timeout on the replicas and clusters.
VSS has IIRC 60 seconds to get in do its...
September 20, 2024 at 3:43 pm
I logged in with my credentials to the sqlserver and not the domain account which the engine is currently running under..
That is a false test, you need to be...
September 12, 2024 at 10:23 am
Thanks for the response @Ant-Green
Also then map the UNC path in windows explorer as the engine account, can the drive map itself? - Yes I was able to map...
September 12, 2024 at 10:10 am
RDP to the UNC server, find the folder, and verify the engine account has full control access to the folder.
September 12, 2024 at 9:44 am
Verify both the share permissions and the NTFS permissions, just because it has access to the share doesn't mean it has access to the actual disk.
Also then map the UNC...
September 12, 2024 at 9:18 am
Have you checked and/or configured MSDTC to allow "remote/network transactions".
What do your MSDTC setting look like on the component services snapin on the linked host.
September 11, 2024 at 7:42 am
Just verify in SQL Server Configuration manager that SQL has actually got TCP/IP enabled in all the right areas, as there's the part for the engine and for the client...
September 5, 2024 at 8:30 am
That's the same problem then, all your connection managers / data sources are having the same issue, so will need to force the connection property NP:
Looks like whatever you done...
September 5, 2024 at 8:27 am
Add TCP: to the beginning of the servername, or NP: if wanting to force named pipes etc.
September 4, 2024 at 3:57 pm
OH, sorry with you saying TCP/IP thought it was going over the network.
Probably try forcing a protocol in the SSRS config manager, like TCP:MySQLServer or NP:MySQLServer in the SSRS connection...
September 4, 2024 at 3:14 pm
Viewing 15 posts - 16 through 30 (of 6,353 total)