Tag Info

New answers tagged

1

I suppose it depends on what you are trying to achieve and how your network is configured. You could test against a single server within your stack via a dedicated VIP to understand the load capacity of a single node, this wouldn't give you a definitive result but would give you some idea of the stack capacity.


0

OK, so the problem was that the server where the SQL Server is running, all in a sudden was removed from the DNS. :-/ Not sure why, the server can ping to the rest of the data center, but the rest of the data center cannot ping or access this server. Rebooting the server resolved this issue.


1

Katherine Villyard's script for detaching / attaching is good. If you want to backup and restore that is also a good option that is frequently used. But do the logins first. Copy the code for sp_hexadecimal and sp_help_revlogin from this Technet article and use sp_help_revlogin to generate TSQL statements that you can use to copy your logins over. The ...


3

By upgrading it, essentially. You have the option of an in-place upgrade, where you run the installer on your existing instance and upgrading it, or doing a migration upgrade, which essentially consists of standing up a new SQL server instance and moving your databases over. The in-place upgrade is easier, but riskier - use the "SQL Upgrade Advisor" and ...


2

There is no clear cut answer to such question, however I will provide you with some links that should set you on the right path of optimizing the VM setup. I would start by reading the official documentation from Microsoft regarding performance: Performance Guidance for SQL Server in Azure Virtual Machines: ...


0

While I have limited experience using MODx, I have over a decade of experience migrating websites. Generally speaking, the two servers could seems similar but can be very different. There are dozens or even hundreds of variable settings that can prevent your old installation from working on the new server. That being said, MODx seems to provide pretty ...


2

Buy the SSD drive that matches your expected workload. From the Dell SSD FAQ: The use of an endurance management algorithm ensures that sufficient Program/Erase (P/E) cycles are available for the warranty time period of the drive. The firmware will limit writes if a drive is written heavily. If you buy the a drive not intended for a write heavy ...


2

Depends on what you're doing to the SSDs. Today, MLC versus SLC doesn't matter as much as buying the appropriate drives with the right attributes for your use case and environment. If that means "write heavy", "read optimized", "low latency", whatever... See: Are SSD drives as reliable as mechanical drives (2013)? But why complicate your thinking? If a ...


1

Assuming you keep it under warranty, if it ever fails, they'll replace it. The expected lifespan is their problem.


0

Check whether the non-working IIS server has "trust computer for delegation" set: http://blogs.technet.com/b/taraj/archive/2009/01/29/checklist-for-double-hop-issues-iis-and-sql-server.aspx


1

Yes this should suffice for your new application, as you will not be needing more then Express edition limits in Storage/RAM/CPU, according to data you put in the question. Your application should not be doing to much load. You haven't mentioned in your question, why are you worried about using SQL Express, are you deciding between different types of ...


4

There are a lot of different ways to migrate the databases. Backup and restore is the most commonly recommended, but if you have more than 100 databases you might want to script something to detach and attach the databases. I've successfully used this to migrate a very large number (hundreds) of databases to a new server: @ECHO ON set ...


2

Backup and Restore the databases as suggested. Then run this microsoft script (https://support.microsoft.com/kb/918992) on the old servers to generate a script to create the logins on the new server. Since you have two source servers, be sure to review your script carefully to make sure there aren't any duplicate entries or other issues.


1

Found the problem in the end. The TCP/IP protocol in the SQL server configuration Manager did not have 1433 set as the port + none of the IP's were active and enabled. Once I enabled and changed port to 1433 and restarted all worked.


0

After looking everywhere and not finding any documentation or advice on this, I decided to do some of my own testing. After the FIM installation was completed and FIM was running properly, I reduced the service account's rights to have only dbowner on the FIM database and no server roles. We've had no issues with this setup, so I consider this to be an ...


1

The "server role" bulkadmin only gives permissions for bulk inserts. Insert, update, and delete permissions are per database (or "fixed-database" roles). So you need to grant these permissions on a per database level. I'm guessing what you want is to use db_datawriter fixed database role, which can "add, delete, or change data in all user tables". You might ...



Top 50 recent answers are included