Tag Info

Hot answers tagged

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 ...


4

You might need to back up your transaction logs more frequently than hourly if your database has a lot of transactions. Every 15 minutes isn't uncommon. I'd suggest editing the maintenance job to run log backups more frequently. Also, does the .ldf have enough disk space? If the physical file is prevented from growing, it'll run out of space even with ...


3

How can I create a network between these 2 computers for file sharing? Connect them both to the same router at the same time. Can I access SQL server installed on 1 computer from 2nd computer? If yes, how? Yes. There's nothing special you need to do. Whatever tool you are using should let you specify the server you want to connect to. Specify 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

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.


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: ...


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

This is poor design limitation, and it is still the case for SQL Server 2014. The SQL Server installer should be able to move everything! However, you can work around it by creating folders where you want (still separate 32/64 bit), moving everything there from the original to the new, then creating junctions that map the new locations to the old. You'll ...


1

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


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 ...


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 ...


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.


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 ...


1

SSMS is basically saying that SQL Server isn't running, or it just can't connect to it. This may sound like a dumb question, but: The service is running, right? Sorry, I had to ask. Also, check and make sure that you have static ports set. SQL Server uses dynamic ports by default, and if your firewall only allows 1433, well, the port might have ...



Only top voted, non community-wiki answers of a minimum length are eligible