Tag Info

New answers tagged

1

You installed the EPEL repository for EL6, but you are running EL7. Remove it and try again with the correct EPEL version.


0

A diff backup is connected to the last full backup taken. Simple like that. I suggest you move the hosting provider taken backups instead of splitting the backup chain.


2

People often have a misconception about the full backup and log backups. In order for the backup to work in FULL backup recovery model, the t-logs must be used, as during the backups there may still be transactions going on in the database (unless you perform a so called COLD backup when you shut down the database). Oracle uses the same concept when you have ...


0

We had a network expert look at this, and it turned out to be erroneous MTU-settings that caused this. From what I understand most of the network infrastructure supported jumbo frames, so the MTU was set to 9000. But there was one component (VPN-tunnel) who didn't support this, so frames over a certain size were truncated. Changing all MTU-settings 1500/1460 ...


2

You said in a comment above that your databases are only about 10GB total. SQL Server can easily load them entirely in memory, including data, indexes, and temporary data from your queries. This is a good thing, and provides better performance than reading from disk.


2

It means that your queries aren't large enough to fill the memory. This is a good thing, unless you are seeing heavy I/O while running the report.


1

I wouldn't actually execute this myself. ;) However. Declare @procid int, @SQL nvarchar(max) SET @procid=60 WHILE @procid < 100 BEGIN set @SQL='kill ' + CONVERT(nvarchar,@procid) EXEC SP_EXECUTESQL @SQL SET @procid=@procid+1 END As for processes from a specific hostname or username: DECLARE @Table TABLE( SPID INT, ...


0

For iis hosting you can use shared configuration : http://www.iis.net/learn/manage/managing-your-configuration-settings/shared-configuration_264#02 For site content you must use "staging" and production concept . One server is "staging" and you push your site with webdploy from a local iis on your laptop to this staging server for exemple . And from ...


1

Hyper-V on 2012 and 2012 R2 has built-in replication of virtual machines. Just enable it and replicate the VM's.


1

It's using SQL Agent Job step tokens (explained here) to set the path to one thing for default instances and another thing for named instances. Then it's using the SQLSERVER provider to get a reference to a (policy?) object for the instance and call a method on it.


1

It's not asking you to restore master. It's asking you to not be in DBASE while you're trying to restore DBASE. Try: USE MASTER GO ALTER DATABASE DBASE SET SINGLE_USER WITH ROLLBACK IMMEDIATE GO RESTORE DATABASE DBASE FROM DISK = 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.DBASE\MSSQL\Restore\DBASE.BAK' WITH MOVE 'DBASE' TO 'C:\Program ...


0

So I want to rephrase the question a bit: Is it normal, that stored procedures or the statements executed by stored procedures never show up in "Recent Expensive Queries"? Chances are those statements where in there (at least if it was above certain metrics [See Below]) but the tool will show the statement only. It's up to the administrator to ...


3

Yes. Both products are part of Microsoft's standard SQL platform. Simply backup your database on the SQL Express platform and restore the backup on the SQL Standard platform. It really is that simple. About the only possible issue I can think of that will make it more than a few mouse-clicks or a couple lines of T-SQL is that you will need to specify new ...


0

The short answer is RBAC - role-based access control. Your permissions to all environments need to be different - and as annoying as things like things like UAC are, you need them: especially for PROD environments. There is NEVER a reason for devs to have direct access to Prod - regardless of how small the organization/team is. Your "Dev" may also wear the ...


-2

In addition to ports required for endpoints(usually 5022,5023), UDP 137 is also needed to be open at both side of mirror. This port is used for network discovery and netbios which is the essential part of mirroring endpoints to be able to talk to each other. Hope this helps.


1

A step by step instruction can be found here: http://www.randomtechtips.com/change-logon-account-for-sql-server-service/ 1 – Create a dedicate domain account to be used for the SQL Server Service – don’t get into the habit of using your own domain admin account to run services – systems will break when you leave and your reputation will be shot! 2 – Using ...


-1

using MS SQLServer 2012, you need to perform 3 basic steps first, generate .sql file containing only the structure of the source DB => right click on the source DB and then Tasks then Generate Scripts => follow the wizard and u can save the .sql file locally Second, replace in .sql file the source db with the destination one => right click on the destination ...


0

This morning i have experienced the exact same unresponsive SSMS (No keystrokes function, have "End Task" via "Task Manager"). My environment is similar to those indicated above; Surface Pro 3 w/ 2 additional monitors (total of three). After killing SSMS, moving SSMS to monitor #1 before closing it works. When I re-open SSMS the dialogue box properly ...


1

Developers shouldn't know the password to the production database. The prod password should be random and not memorable — something like the result of keyboard mashing (Z^kC83N*(#$Hx). Your dev password can be $YourDog'sName or correct horse battery staple or whatever. Sure, you could find out what the password is, especially if you're a small team, by ...


25

I disagree with the assumption in the question —this is security— but I also disagree that automation is going to save the day on its own. I'll start with the problem: You shouldn't be able to accidentally do anything to production! That includes doing automated things accidentally. You're confusing system security with concepts like "who's allowed to do ...


12

One of my coworkers has an interesting approach to this. His terminal color scheme for production is fugly. Gray and pink and hard to read, which is theoretically supposed to ensure that whatever he writes, he really intended to write. Your mileage may vary... and I probably don't have to say that it's hardly bulletproof on its own. :)


29

If this is something you see yourself doing often, automate it. And since you're both developers, writing some code should be in your wheelhouse. :) Seriously though... by automating it, you can do things like: Verify that you're restoring on the correct server (i.e. no dev -> prod restores) Verify that it's the right "type" of database (in your case, ...


0

You haven't mentioned what you're using for storage, but if you're using a SAN you could also use SAN replication with your SQL cluster. If you don't already have the various pieces for that, however, Always On might be a better option. (Like Jim B suggested.)


2

Always on would let you have separate storage for each node. (http://msdn.microsoft.com/en-us/library/ff877884(v=sql.110).aspx) However this gets trickier in win10 with the new storage HA features.


1

I used the workaround posted on that Connect page by "Kyle Neier". That worked for me. Simply replace the PowerShell code in Step 3 of the SQL Agent Job with this: $SQLServerConnection = New-Object System.Data.SqlClient.SqlConnection $SQLServerConnection.ConnectionString = "Data Source=$(ESCAPE_NONE(SRVR));Initial Catalog=master;Integrated ...


1

This is taken straight from the manual, please consider it as a requirement: You cannot run SQL Server services on a domain controller under a local service account or a network service account.


0

Joel, Please review this one: http://msdn.microsoft.com/en-us/library/ms178142(v=sql.105).aspx I think the domain users do not have the login as a service right. Best, -Iulian


4

Answering your comment: If you install SQL Server on D: and Windows runs on C:, SQL data will live in: the MDF and LDF files (on D:), in TempDB (on D:), and in Memory. It's possible in a severe low memory state for the data to get swapped to the page file, which may live on C:. Locking pages in memory may help. SQL 2014 should support this. See ...


9

Disclaimer: I am not a lawyer. First, some required reading: Microsoft Azure Trust Center HIPAA Business Associate Agreement (BAA) HIPAA and the HITECH Act are United States laws that apply to healthcare entities with access to patient information (called Protected Health Information, or PHI). In many circumstances, for a covered healthcare ...


1

You've understood the process correctly. You need to set up two user accounts. One would be created on the SQL Server host, the other one would be created on the client you want to connect from. Their usernames and passwords should be identical. SQL Server prefixes the username with hostname or domain name, however that is not a problem, Windows ...



Top 50 recent answers are included