New answers tagged dba
The DBA StackExchange was made to address technical and strategic aspects of DBMS products and deployment of such into infrastructures. When it comes to dealing with difficult DBAs, there is no black-and-white answer to offer. In your particular case, I will make an exception. I answered two interesting posts four(4) years ago May 02, 2011 : How could ...
You could stop the passive node, drop it out of the cluster, unplug its LAN cable or otherwise disable the passive node before restarting the acitve services. The consequences could be .. um .. "intertesting", depending on how cleanly this process is handled and how skilled the tech team that configured the cluster were.
Do a back-up/ restore - takes longer but appears to be a favoured method. This is what we prefer. -- Backup and Restore. Safer Method. Option to detach the database using sp_detach_db and then attach it using CREATE DATABASE ... FOR ATTACH; or detach and attach using the GUI will actually detach the database from the source server. Many things can ...
The backup/restore method is generally my preferred way especially if you're on 2008R2 or higher due to backup compression. If you don't have access to that feature, the backup file generally is still a smaller file copy than the .mdf/.ldf file copy because a backup file removes any wasted space in those database files
This is explained here, it boils down to that you have to have a full backup of the databases as well as a backup of the read-only filegroups: A piecemeal restore sequence restores and recovers a database in stages at the filegroup level, beginning with the primary and all read/write, secondary filegroups. In this example, a database named adb, ...
One of the considerations implementing multiple databases is different RTP/RPO requirements. It seems this is the case in your situation because the RPO is different. Consider creating a separate databases for the ETL tables and historical data. Backup the historical data database as needed to meet your RPO. The ETL database can be backed up ...
Not only is it a best practice, it's mandatory to any major compliance requirements such as PCI V2 & V3, SOX, and almost any auditor will ask about it. Yes, having them on the same network is asking for major problem. Page 5 of the PCI DSS V2: For example, there must be a clear segmentation of functions and segregation of networks with different ...
I have to say yes. By blocking dev/test you are making sure that application changes are not accidentally updating production data. In many cases sensitive data on dev/test is scrubbed after restore and by blocking you are making certain that no one with access to test can access sensitive data in production. If you are using SQL Server with MSDN licensens ...
I have since come to learn, from this SO thread, that it is possible to do what I asked in my question. And it prevents rows inserted/updated/deleted on the source from being replicated to the destination.
I believe your DBA is referring to Publishing Stored Procedure Execution in Transactional Replication. With Transactional Replication you have the option to published the definition of the stored procedure or the execution of the stored procedure. Publishing stored procedure execution can provide significantly better performance for large batch operations ...
The value -1 is a special value that means "maximum currently supported". The maximum length of e.g. max, xml, and clr types could change in a future version of SQL Server. In system views like INFORMATION_SCHEMA.COLUMNS the CHARACTER_MAXIMUM_LENGTH column already uses NULL for types where a character length is not applicable, for example the numeric types. ...
Don't know if you'll get a good answer why, I suspect the person who made that decision didn't like NULLs, which would have been better IMHO.
OK - this should be easy for the first part, if you're willing to be a bit adventurous :-). MariaDB has had computed columns (otherwise known as virtual or generated columns) for quite a while now. Otherwise, the latest milestone release of MySQL (5.7.7) also has them. If you want to do this with a current GA version, you'll have to use TRIGGERs. However, ...
My $0.02; perform the calculation app side. It will scale better. Its possible to perform the calculation in an update or an insert on duplicate key update statement.
Top 50 recent answers are included