I am trying to enable file stream on Microsoft SQL Server 2017, on a Windows Core 2019 Server.
I have changed the registry settings at the following location to enable it as there is no GUI. I set the value to 3
ServerName\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL14.InstanceName\MSSQLServer\Filestream.EnabledLevel
After This I restarted
I have also installed the latest Cumulative update (20) as I know there where issues with Driver signing.
After This I restarted
I am seeting the following Errors in the log file at C:\Program Files\Microsoft SQL Server\MSSQL14.InstanceName\MSSQL\Log
<{781FAE78-09AB-4EE5-B051-67747BDB19E3}>RsFxMgmtInitialize failed (the RsFx device is not found. Check if RsFx driver is started.): Error 0x80070002 (-2147024894)
2020-04-21 08:56:03.94 spid5s FILESTREAM: failed to connect to kernel driver RsFx0503.
<{1038F43D-3391-45F7-B1B3-BADF26459429}>Failed to initialize CFsaShareFilter: Error 0x80070002 (-2147024894)
<{1038F43D-3391-45F7-B1B3-BADF26459429}>Failed to initialize CFsaShareFilter: Error 0x80070002 (-2147024894)
2020-04-21 08:56:03.94 spid5s FILESTREAM: effective level = 0, configured level = 2.
2020-04-21 08:56:03.94 spid5s FILESTREAM feature could not be initialized. The operating system Administrator must enable FILESTREAM on the instance using Configuration Manager.
SELECT ##VERSION
Microsoft SQL Server 2017 (RTM-CU20) (KB4541283) - 14.0.3294.2 (X64) Mar 13 2020 14:53:45 Copyright (C) 2017 Microsoft Corporation Standard Edition (64-bit) on Windows Server 2019 Standard 10.0 <X64> (Build 17763: ) (Hypervisor)
I got this working on one server and cannot get it working on the second one.
There is also a version of sql 2019 on this box
Any help? Also any advice on getting this working on a cluster
I used "computer management" and remotly connect to your core server. From there, you can enable FileStream and configure it.
This seemed to work better that the registry method
Related
I recently started using sys.dm_os_enumerate_filesystem.
My SQL Server version is:
(Microsoft SQL Server 2017 (RTM-CU31) (KB5016884) - 14.0.3456.2 (X64) Sep 2 2022 11:01:50 Copyright (C) 2017 Microsoft Corporation Developer Edition (64-bit) on Windows Server 2012 Standard 6.2 (Build 9200: ) (Hypervisor) )
Everything worked fine until I started querying filesystems where the directories are very large.
The following query generated the error:
SELECT *
from sys.dm_os_enumerate_filesystem('F:\technician','*');
Msg 407, Level 16, State 1, Line 15
internal error. The string routine in file sql\ntdbms\storeng\dfs\alloc\storagedmv.cpp, line 799 failed with HRESULT 0x8007007a.
The directory is 460 GB. I have also checked all permission and SQL Server service has all permission on the above directory.
As you can see the SqlServer is running with the last CU31.
Is there a workaround?
I need to migrate several DTS packages as noted above. They're actually running fine when I run them via dtexec.exe on the command-line. But if I try to install and run them via SQL Server Agent - as they were previously and as such are supposed to - I get the bogus error message, that
C:\Windows\Temp\.NETFramework,Version=v4.0.AssemblyAttributes.vb
...couldn't be accessed. I say bogus because this (generated?) file is actually there and should be accessible since I'm running all of this logged into SQL Server via Windows Authentication as local administrator.
(Update: I should explicitly mention that I've tried creating and running these jobs off the SQL Server Integration Services as well as directly off the file system. Both methods end up with the same result described above.)
After trying to read up on the matter I got the impression that you migrate such packages correctly by installing Visual Studio / Data Tools / Integration Services, loading the DTS packages in there, inspecting and fixing any errors - i.e. rebuild the whole thing in the new IDE. So I set out to do that, and got a bunch of the following error messages for VisualBasic scripts within the DTS package:
The binary code for the script is not found. Please open the script in the designer (...)
I did that, and was notified about a missing type:
BC30002 - Type 'Microsoft.SqlServer.Dts.Pipeline.SSISScriptComponentEntryPointAttribute' is not defined. (...)
This seems really weird, because I'm able to open the type's sources in question in Visual Studio without problems.
Why does this happen and what can I do about this? Why do I need to bother with all of this if the DTS packages run fine with dtexec.exe on the command-line?
Exact server versions:
Microsoft SQL Server 2012 (SP4-GDR) (KB4583465) - 11.0.7507.2 (X64)
Developer Edition (64-bit) on Windows NT 6.3 (Build 9600: ) (Hypervisor)
Microsoft SQL Server 2019 (RTM) - 15.0.2000.5 (X64) Sep 24 2019 13:48:23 Developer Edition (64-bit) on Windows Server 2019 Standard 10.0 (Build 17763: ) (Hypervisor)
I want to know who has modified the table in the SQL server, But I couldn't find any authentic solution for this.
I tried function fn_dblog, but it is not allowing me due to some permission issue.
SELECT * FROM fn_dblog(NULL, NULL)
Error Message:
Msg 229, Level 14, State 5, Line 1 The SELECT permission was denied on
the object 'fn_dblog', database 'mssqlsystemresource', schema 'sys'.
I refereed this article, but the link for the fndblog2 function expired.
Basically, I want to get the list of users who have updated the given table, if it is modified in SSMS then user details and if it is modified by some .net application then .net application name.
SSMS details: Microsoft SQL Server 2019 (RTM-CU10) (KB5001090) - 15.0.4123.1 (X64) Mar 22 2021 18:10:24 Copyright (C) 2019 Microsoft Corporation Developer Edition (64-bit) on Windows Server 2019 Datacenter 10.0 (Build 17763: ) (Hypervisor)
Note: Privelleged Permission can't be given to me due to securities issues. I am fine with writing a C# application. I am ok with writing C# appication if it is possible in C#.
I am getting this error in SSIS
****Exception from HRESULT: 0xC0202040
Error at <Task name> [OLE DB Destination [81]]: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E21.
An OLE DB record is available. Source: "OraOLEDB" Hresult: 0x80040E21 Description: "Multiple-step
OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.".****Error at Populate datacombined data [OLE DB Destination [81]]: Failed to open a fastload rowset for <Table name>.
Check that the object exists in the database.
Please can anyone tell me if the installed versions of software are correct for the below mentioned version of visual studio and Sql server which is installed on my machine:
I am using 64bit- windows 8.1 enterprise.
Sql server : Microsoft SQL Server 2008 R2 (SP2) - 10.50.4000.0 (X64) Jun 28 2012 08:36:30 Copyright (c) Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 6.1 (Build 7601: Service Pack 1) (Hypervisor)
Microsoft visual studio : Microsoft visual studio 2012 shell version 11.0.50727.1
32-bit Oracle Data Access Components (ODAC) with Oracle Developer Tools for Visual Studiobase.
ODTwtihODAC : ODTwithODAC1120320_32bit
64-bit Oracle Data Access Components (ODAC)
ODAC121010_x64
Attunity : I installed attunity version 1.2 -- 32 and 64 bit.
I am able to connect to the oracle DB and able to fetch the data, but the problem is in data access mode of the destination oracle server. It's throwing the error when I set the data access mode as table or view - fast load.
Can anyone please help to resolve this issue. Is there any setting which I need to change in visual studio after installing attunity?
Please note that this is an already existing package and I am trying to open and run it. This package does not throw any error in another machine with data access mode as fast load.
Thanks in advance.
I think this is what you really need to use the correct version of the driver.
In order to force VS to use 32 or 64 libs go to Project Properties->Configuration Properties->Debugging and change Run64BitRuntime.
I don't think that is the correct version of the Attunity Connector. For connecting to MSSQL 2008, we are using 2.0, 3.0 and 4.0 all installed together. I would read the version descriptions that you can get to from here: https://learn.microsoft.com/en-us/sql/integration-services/attunity-connectors?view=sql-server-2017
Since we upgraded some of our Azure SQL servers to V12, we can no longer restore a bacpac locally using command line sqlpackage.exe. We also tried using Management Studio, but no dice.
Our local developer machines are running:
Microsoft SQL Server 2014 - 12.0.4213.0 (X64)
Jun 9 2015 12:06:16
Copyright (c) Microsoft Corporation
Developer Edition (64-bit) on Windows NT 6.3 (Build 9600: )
Here is the error we encounter:
*** Error importing database:Could not import package.
Error SQL72014: .Net SqlClient Data Provider: Msg 33233, Level 16, State 1, Line
1 You can only create a user with a password in a contained database.
Error SQL72045: Script execution error....
This looks like it is having issues creating the users that were added by scripts.
Is anyone else running into this issue?
Update:
Apparently this has been a reported problem since April. https://social.msdn.microsoft.com/Forums/sqlserver/en-US/85bb12e8-5ae4-409c-93fa-8a9d025c6b35/error-when-importing-a-datatiers-application-from-azure-db-as-contained?forum=ssdt
The work around from the above post works. You need to modify the bacpac file and create a new checksum: http://inworksllc.com/editing-sql-database-azure-bacpac-files/
This is a workaround, not a fix.
Update: Looks like there will be a fix soon.