Jump to content

neruve

Members
  • Content Count

    20
  • Joined

  • Last visited

Community Reputation

0 Neutral

About neruve

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Would anyone like to take on the role of adding SSIS into a Microsoft SQL Server 2019 container? Getting MSSQL running in a container is pretty easy but adding SSIS into it is beyond my knowledge base and linux skills. These links should provide all details needed. The easy part, adding this to unraid - https://hub.docker.com/_/microsoft-mssql-server The hard part, getting this inside the container - https://docs.microsoft.com/en-us/sql/linux/sql-server-linux-setup-ssis?view=sql-server-ver15 I'm thinking you would have to start with an ubuntu 16.04 base image and install SQL Server along with SSIS and then turn it into a container. But it needs to have all the options of the mssql docker above as you would want to be able to decide on the version, if you wanted the agent, ports, host path mappings etc. It would also be cool to have SSIS as a flag variable as well. Here is the release notes from Microsoft for SQL Server 2019 - https://docs.microsoft.com/en-us/sql/linux/sql-server-linux-release-notes-2019?view=sql-server-ver15 If anyone decides to take this on and is successful, please please tell me the steps you took to get it done as I would really like to learn but even getting sql server itself to install and run in a base ubuntu container isn't working out for me.
  2. @gfjardim Yes, it did indeed delete the partition, however, the partition name was always still there after the delete with a size of 0b and the format button did not appear. After preclear was removed both of those issues were fixed. When you deleted the partition nothing was shown at all when you click the little plus to the left to view the partitions and the format button was available. Also thank you and @dlandon for the quick response and attention in getting everything resolved. It's what makes this community so great!
  3. It popped the box up asking to type yes. Then it actually did delete the partition, but then after UD refreshed the partition name was still there at 0b and the option to format never appeared. When I uninstalled preclear disks everything worked as normal.
  4. So I guess just only install preclear when you need to preclear a disk and you will probably eliminate the problem?
  5. When I hover over the 'x' it says "Remove Partition". But you nailed it! When I removed the preclear plugin it worked as expected and let me format the disk. Now the question is is the incompatibility on UD or preclear?
  6. So I'm having trouble trying to format a disk in UD. I DO have the UD+ plugin and destructive mode enabled. The drive is a NTFS drive from a windows server box that I replaced with Unraid. I have delted the partition and it seems to have worked as the drive shows 2tb free if i mount it. However, no matter what I do I cannot seem to get the option to format. When I delete the partition with the red x it just comes back wit the same name/serial as the drive itself. The disc log even says that it deleted it. But when I do UD refreshes and its still there with 0b so I never get the option to format the disk. Any insight? This is the first time I've tried to do anything other than mount with UD since you split them into two plugins. I'm on Unraid 6.8.2
  7. This is a little above my head. Any other info you can provide or links on where to start?
  8. Okay, so i'm trying to run these commands inside my sqlserver docker. https://docs.microsoft.com/en-us/sql/linux/sql-server-linux-setup-ssis?view=sql-server-ver15 However, I can't do anything, sudo doesn't exists, curl doesn't exist and when i try to install curl i get the following: $ apt-get install curl E: Could not open lock file /var/lib/dpkg/lock-frontend - open (13: Permission denied) E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), are you root? i'm a complete n00b here as far as things inside a container. Can anyone provide any insight?
  9. I don't know if this is possible or not. I'm not super familiar and still learning. Is there a way to run a script after creating and starting the container for the first time? My current use case is that I have an MSSQL container and I want to enable SSIS but its a seperate install. So I would like to create a script with the commands to install SSIS everytime the container is created (or updated) but it needs to only run one time on the initial startup of the container. Anyone have any suggestions?
  10. Even when i pull the 2019-GA-ubuntu-16.04 it still says apply update every time I check for updates. For some reason it thinks there is always and update. Is it because I built the template myself?
  11. One other thing I can't figure out. It always says there is an update to the container I made for mssql. Do you guys experience the same problem? Is there a fix where it will look at the repo to see if there is actually an update?
  12. Oh where to start. I’ve only been using unRaid for about two weeks. I love how easy it is to get up and running. It’s very impressive. I have very minimal Linux experience, no docker experience and I was able to to replace everything my windows server was doing and then some with ease. I love how easy it is to add storage that is still protected. I also appreciate that LimeTech doesn’t feel the need to do everything themselves. There are containers that do things very VERY well and there is no reason for LimeTech to spend time and maintenance to implement things that are already handled (and that won’t apply to most users). As far as new features. Multiple SSD supported pools would be nice as others have mentioned although I haven’t personally felt the need to have them I can see where they would be preferred. I mostly just want them to focus on core functionality that applies to every user, not just things that some users want. Actually, back to one of the best things about unRaid as mentioned above (they don’t feel the need to implement everything and maintain it) it would be kinda cool for like, unRaid approved/recommended containers. They could work with the developers. Like binhex, linuxserver etc and maybe work things out to ensure updates , support etc. then they can be aware of developer a getting out of the game and can find developer b to take over with the same or another solution. I hope that makes sense. It makes sense to me haha. On another note. Shout out to the community for being so awesome!!! EDIT: I actually would really like to see shadow copies. Like I want share x to be on all my drives. But I’d also like to see it locked down a bit. Like. A size limit in relation to a percentage of the smallest drive etc. (as it should really only be used for important things) it would also be cool of you could sync that share with cloud storage as well)
  13. Thank you all for the help with this. I was able to get Sql Server running great on my unraid setup. I would also recommend adding the Enviroment variable MSSQL_AGENT_ENABLED so you can set it to true or false to make things complete. I also added in the Enviroment variable MSSQL_PID so it can be set to different license versions, (default is developer, but you can set standard, express, etc) Now what I can't figure out is how to get SSIS in the mix. Anyone have any ideas? I think it also needs an integration server but i'm not sure.
  14. Last one, sorry guys! I figured it all out. Figured I would post the solution here in case anyone else has the same issue. I stopped the array, then went to Tools > New Config as suggested in first replay. This reset my array. Then I added the 8tb drive (the one with data on it) to the array along with my cache drive. Then I put the usb drive inside the hot swap bay on the server, the filesystem wasn't recognized, then i did a format to xfs and I was able to add it to my array just fine. So there was some sort of issue with the drive being plugged in via usb instead of mobo sata that unraid didn't like. Something must not match in the drive signatures or something. Which is a little odd as it seems unraid uses drive serial numbers and that didn't change.