Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 4 years ago.
Improve this question
Do you know of any impact on the ClearCase application for the below mentioned Microsoft patches?
My environment is Win 2003 Enterprise SP2
Security Bulletin Risk Description KB Number
MS14-017 Critical Vulnerabilities in Microsoft Word and Office Web Apps Could Allow Remote Code Execution KB2949660
MS14-018 Critical Cumulative Security Update for Internet Explorer KB2950467
MS14-019 Important Vulnerability in Windows File Handling Component Could Allow Remote Code Execution KB2922229
MS14-020 Important Vulnerability in Microsoft Publisher Could Allow Remote Code Execution KB2950145
It depends on the nature of the ClearCase running on your server:
simple Base ClearCase client
ClearCase Vob server
CCRC server
Unless you see a warning from IBM, you can proceed with the installation, and double-check with IBM (communicating at least the full version of your ClearCase setup: cleartool -verall)
You can see some general advises in this thread:
VOB servers are specialized. Normally patches and service packs provide no benefits or improvements.
Does your IT department test patches and service packs before installing them enterprise wide? Blindly trusting any windows upgrade/sp has been empirically shown to be a Bad Idea(tm).
Get management involved. Yes patches and sp's are important, but so is having a working VOB server. If folks understand the risks to the company, they'll be more keen to work out a compromise. (Don't fall for the "we'll give you control of the server and you'll be in charge of patching it.")
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 1 year ago.
Improve this question
I like SSIS, I already created packages but I don't have SQL Server license.
Can I run the package and get scheduler in server?
Nope.
You have a developer license which is quite clear what constitutes development (development tasks only - you touch prod, you're engaged in production work)
Using hacks to run devenv.exe and launch packages are clear intent to circumvent licensing. Carefully copying assemblies and patching a box to support "bad" actions is even more egregious license violation.
What happens when your organization is audited by Microsoft? There's the "oh, we noticed these license violations. Let's get those fixed, please. Maybe you should buy some azure credit to offset the penalty." Harm determined, minor penance required.
Then there's "Oh, you were malicious about breaking the rules. We have more lawyers and accountants than you can imagine." Harm determined and hell is coming with us.
It's not you that will be hauled to court, it's your organization and you can bankrupt them (if you use Enterprise Edition parts that can be a hefty bill).
You either pay for what you use or spend your time rolling your own implementation. Some of it's not hard (copy data from one table to another). Others are far more devilish.
Integrating David Browne's excellent comment on pricing for SSIS in ADF vs VM
Prices for SSIS in Azure Data Factory start from under 0.60USD/hour. And you can start/stop the SSIS runtime from an ADF pipeline. Pricing for SQL Server Standard Edition on an Azure VM is similar.
https://azure.microsoft.com/pricing/details/data-factory/ssis
https://learn.microsoft.com/azure/data-factory/how-to-schedule-azure-ssis-integration-runtime
https://azure.microsoft.com/en-us/pricing/calculator
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 4 years ago.
Improve this question
We will be starting our migration soon and got following questions.
Platform --> Windows 2003 to Windows 2008
ClearCase --> 7.1.1.2 to 8.x
Clients also Windows.
Got around 200 users and about 120 VOBs data size is about 900 Giga. IBM recommend 16 GB and quad core processor. But is this sufficient for 200 users?
We got about 20 VOBs configured for multisite with one site which is closed now. Should we require multisite license? Is there any way to make it use normal license.
IBM recommend 16 GB and quad core processor. Is this sufficient for 200 users ?
Yes, I used similar specs. The real limitation isn't around the users, but the number of vobs managed, and their associated vob_server.exe.
Also, check the ClearCase system Requirements for Windows.
We got about 20 VOBs configured for multisite with one site which is closed now.
I would recommend at least one multisite license to complete the migration, but once the export/import is done, you could simply remove all replica registered to the vob, and see if that vob can be used with a simple ClearCase regular license.
(Although the vob itself seems to remember the deleted replicas)
If the VOB remains replicated at the end of these procedures, MultiSite licenses will be required for all users who will be accessing the VOB.
The steps assume that this is a 1 way move, and that you wish to de-replicate all VOBs after having "moved" them to the new host. The resulting VOBs will not draw MultiSite licenses once complete.
Remove the original replica from the new replica family.
Example:
multitool rmreplica replica:<source-site's-replica>#<local-vobtag>
This is now a de-replicated VOB and will no longer require a MultiSite license.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
Quick Question: Is it possible to mirror a database without downtime?
Long Question: I have a database on production being used by quite a few clients. The previous management did not implemented any kind of redundancy or high-availability strategy (no clustering... not even storage!!!), and now, as business grows, this is becoming a huge liability... as a emergency act I'm considering mirroring the database... The main problem is that I cannot take down the database. That would imply on some legal/financial problems due to some previous SLA agreements... So, can I mirror a database without taking it down?
Extra info:
The SQL Server version is 2008 R2 Enterprise.
The instance consist of one database only (it's a multi-tenant database)
The database infrastructure consist of one physical server running windows 2008 R2 (standalone server). It's not a cluster nor a VM and theres no storage behind it... all data is inside it's only 2TB disk...
The Database size (.mdf) is about 170 GB...
There's about 100 transactions each second
There's no hours when usage goes down... business are 24/7...
Yes, this totally looks like that environment a developer would create on their machine...
This is all in books online. Hopefully you can try in development, or on your desktop first. There are quite a few things to consider, so you should give it a thorough read.
Yes, you can mirror without taking it down. You restore a backup to the mirror and use NORECOVERY option. You then setup the mirroring and transactions start to move from primary to mirror. You'll need to set up any other things needed on that remote server - logins, jobs, etc.
Transfer logins using this method, so you get matching SIDs between servers.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I'm seeking for a solution to monitor (with graphs) the status of my MSSQL instances during a periode of time (day or night) and get or make reports for that monitoring.
Does any one have or know any known simple solutions to do so please ?
Thank you for your help.
Depends on what you want to monitor. There are vendor products that will do it. Idera has Diagnostic Manager and RedGate has SQL Monitor to name just a few. Or if you don't want to spend any money SQL Server has several monitoring options including alerts, policy based management and data collection. These won't be as pretty and may not cover as much not to mention you will be writing some code on your own, but they are free (with SQL Server of course, depending on edition).
Related, though you'll want to edit the scripts for getting information is Ola Hallengren's maintenance solutions http://ola.hallengren.com/. There are useful scripts for maintenance, but depending on what information you're trying to obtain, you can build on these scripts to get information. From there, you can use the results of these queries in SSRS to populate graphs, or even use a tool like Excel.
Again, Ola Hallengren provides maintenance solutions, so these will need to be adjusted for monitoring (depending on what you're monitoring), but they are totally free and you can edit the scripts, as well as see where the information comes from so that you can determine what you need to monitor.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I have here a situation. I have a almost release ready (release in 2 month) application that runs queries on the microsoft Sql-Server database.We use the standard Microsoft jdbc driver implementation for sql-server. Works great,no problems.
Now there come a developer to me and says that i we should switch our default jdbc implementation to the the JTDS driver implementation.
I read in the web a little about the driver and its benchmarks and so on , and it really seems to perform a little better the the driver from Microsoft.
But taking in consideration the release soon and that the driver is opensource and all the other stuff that i currently dont think of it right now , would you invest your time to make the switch?
I've used the JTDS driver in production for around a year without any problems.
However, in your case, if you've got a system that been built and tested with the MS JDBC driver, then you really ought to stick to that.
In the meantime, conduct some tests and see if you can collect hard figures that show JTDS outperforming MS JDBC for your use cases. If the data back up these assertions, then come up with a plan to start using JTDS in your development and test cycles, finally rolling it out to your production release.
We are using jTDS drivers for about an year. As of today, I can tell the following:
Pros:
Smaller JAR.
ResultSets are faster. Fetching is configurable.
Caches huge results on disk (MS driver requires you to use slow bidirectional cursors or caches results on memory, yielding occasional OutOfMemoyErrors).
Documentation is small but enough (MS driver documentation is spread in hundreds of MSDN pages).
Better error reporting (always a nice SQLException, while MS driver sometimes gives ClassCastException or other RuntimeException).
Open source.
Cons:
Bad support, due to:
Relatively small user base, giving bad community support.
Not backed by a big company, so if you need some solution fast, you must hope the developers are available and willing to help (and remember they are not paid for answering forums messages).
Because MS SQL Server protocol has many proprietary parts, MS can perform changes that break jTDS when you apply maintenance updates on the server.
Not as up-to-date as the MS driver. When MS launches a new SQL Server version, the JDBC drivers are usually released together. jTDS must work to catch up and that may take months.
Close to release, no.
Do it later, yes.
JTDS has benefits over the MS one such as you can use a domain service account for your SQL connection and supports encrpyted SSL.