Comments
-
I have seen some information about a future release leveraging SQL 2016 to store the Netflow data but nothing today. I am also in the same position and am thinking of using a windows cluster and creating a generic service role for the application, not sure if it will work or be supported but worth a test.
-
Agreed, i only found this thread by clicking browse and content! The bottom section was a way to see what was trending from the community rather than what is trending from the SW staff. Bring it back!
-
Had this exact same problem which was down to the user account being used in SNOW. For us something changed in our SNOW instance and the rights the user account needed got lost, we checked the account and logged a ticket with support but their first suggestion was to give the SNOW account admin rights. We did this and it…
-
Did you "Copy" the account from the server the DB was first installed on to the secondary nodes? Reason i put copy in quotes is because it's not a straightforward recreate the account with the same password.
-
Dragging up my old post. Does anyone who has done the upgrade to 12.4 know if it removes this component or if you have to manually uninstall it afterwards? Thanks
-
Question 12 won't let me pick all the answers, it's like a moving dot
-
Welcome to THWACK
-
Regarding the virtual hostname being optional. We are planning a large scale deployment with multiple APE's and AWS's to front the web console and polling/node traffic. The primary polling engine will be in a HA pool and ideally in a multi subnet setup and in essence just the brain, if we leave the virtual hostname blank…
-
If it's a single server install failover clustering and make it a single node cluster, add the old name and ip as resources into a role and your set. If it's a cluster already then you could do the same but get a DBA involved to make sure SQL is part of the same role so it fails over cleanly
