Viewing 15 posts - 1 through 15 (of 83 total)
My current solution is to switch the Linked Server to ODBC instead of OLEDB
EXEC master.dbo.sp_addlinkedserver @server = N'<linked_server_name', @srvproduct=N'', @provider=N'MSDASQL', @provstr=N'Driver={ODBC Driver 18 for SQL Server};Server=<server_name>;Trusted_Connection=yes;TrustServerCertificate=yes;Encrypt=yes;'
However a...
November 15, 2023 at 2:36 pm
Thank you Ken, this would be a mitigation of the problem.
As it is currently only used in stored procedure, is there a hint (SET something), so that I do not...
October 25, 2023 at 1:56 pm
Hi,
I tried this option but it does not change the behaviour. I tried also the option from the driver settings, however I am just doing a SELECT in the procedure...
October 25, 2023 at 8:35 am
Hi DinoRS,
thx. It seems to be a solution, after browsing the information and the documentation of JDBC-drivers at MS.
However I did not see any reference to SSIS. Is it possible...
September 25, 2019 at 3:23 pm
actually no,
if you run it like thisDECLARE @value varbinary(8000/max) = 0x123456789
SELECT *
FROM table
WHERE encrypted_column = @value
March 7, 2019 at 6:38 am
currently this encrypted deterministic, so same value = same varbinary.
If it is possible, what would be the syntax for that?
March 7, 2019 at 6:14 am
Hi Lowel,
thanks for your reply. I am actually not using SSMS. This is a task in an ETL (dtsx-Package).
I am using OLEDB-Source for that specify task....
March 7, 2019 at 5:29 am
Hi Vinoth,
what I did is, to create a dedicated schedule that ended in the past e.g. 01.01.2017. For every subscription that I wanted to trigger when the data...
April 4, 2017 at 1:52 am
Additionally if you do not have no SA you always have to licence the newest version
In your example SQL 2012 + 2014 you need a Licence SQL 2014 or...
November 2, 2015 at 8:32 am
This is how you can fix it, before MS delivers the right solution:
After the package is migrated you find in the XML-Code following part
<DTS:DesignTimeProperties><![CDATA[<?xml version="1.0"?>
<!--This CDATA section contains the layout...
June 23, 2015 at 3:01 am
It would work, when the sql writes the result in a table instead of using it in a dataflow.
Properly it would get quite confusing, when you have 20-30 page size...
June 19, 2015 at 5:28 am
I opened an SQL Connect Bug
https://connect.microsoft.com/SQLServer/feedback/details/1438953
June 16, 2015 at 3:49 am
the devil is in the details...
Thx for clarifying this
Christian
May 19, 2015 at 6:52 am
Hi Gila,
do you have any M$ documentation for that?
I did not find anything in the description of the SQL Server 2014 descriptions and Upgrade Advisors.
🙁
Christian
May 19, 2015 at 6:36 am
I used the code from the site mentioned above and modified it a little bit.
I wanted to go through all our dtsx-Packages and at the Variable if it did NOT...
January 12, 2015 at 8:04 am
Viewing 15 posts - 1 through 15 (of 83 total)