Hot answers tagged

8

If you are asking whether it is possible to enforce the database defaults for every connection that ever happens on the server, then no. Those defaults only take effect if something contradictory isn't set at the connection level. In any individual batch in SSMS you can use statements like SET ANSI_NULLS ON, SET ANSI_NULLS OFF, SET QUOTED_IDENTIFIER ON, and ...


5

Use extended properties. It's not in the INFORMATION_SCHEMA views but it will stay attached to that object. I wrote about it in detail here: https://sqlstudies.com/2015/05/18/extending-your-metadata-with-extended-properties/ But here is what it would look like attached to a User: Here is how you would query all of the extended properties for users in a ...


4

Right click on the SSIS Catalogue, highlight Reports, and select All Executions. The Simple Talk article, SSIS 2012 Projects: Deployment Configurations and Monitoring by Feodor Georgiev, includes the following illustration: If you are not observing the Reports submenu, try running Setup again and choose Management Tools – Complete. Try executing SSMS ...


4

Vendors will need to catch up, as the add-in model and API have changed. This will lead to better extensibility, but for now you'll need to wait for the vendors to do this work. There is usually not much advantage to doing all of that work while the product is still in beta and the add-in model is still changing (the version of SSMS released on Friday is on ...


3

In the past, the releases lined up - each new SQL Server was accompanied by a new Management Studio. However, in June of 2015 (concerning SQL Server 2016 and onwards) MS announced separate life cycles: With the release of SQL Server 2016 Community Technology Preview (CTP) 2.1, customers can for the first time experience the rapid preview model for ...


3

First off... I think it is best to come clean to your manager on such issues. The business will notice the missing data and he will not appreciate being blindsided and not having all the facts at hand. In that event, things will be even worse for you. If you have no formal background in DBAing, you have no business doing DBA tasks and/or the real ...


3

Come clean ASAP. The sooner you do this the better. If I'm reading the timeline correctly, when you restored the FULL backup over your production database you broke the backup chain. This means you wont be able to get the data for 06:30PM to 10:00PM into your current database that holds data for 01AM to 06:30PM + new data since the RESTORE. I would ...


3

Here is a simple script that might help you. Works for me on SQL Server 2008 sp2 select @@version --Microsoft SQL Server 2008 (SP2) - 10.0.4000.0 (X64) --Sep 16 2010 19:43:16 --Copyright (c) 1988-2008 Microsoft Corporation --Enterprise Edition (64-bit) on Windows NT 6.0 <X64> (Build 6002: Service Pack 2) Part 1: ...


2

From BOL (SSMS Release notes), recent versions of SSMS are outside of SQL Server release. release of SQL Server Management Studio (SSMS) is a stand-alone install outside of the SQL Server release. Our goal is to update this frequently with new functionality, fixes, and support for the newest features in SQL Server and Azure SQL Database. As far as ...


2

+1 for sensibly wanting to get the backups on a separate drive. However, if the new cluster volume is on the same SAN, you're not really accomplishing much. It would likely be much better to run backups to a file share on a totally different system. As a workaround, you can easily add an "Execute T-SQL Statement" task to your Maintenance Plan to manually ...


2

It might be latency, or it might be something else. Run a SQL Server Profiler trace on the remote DB, starting the trace just prior to connecting via SSMS remotely. IntelliSense works by running queries to get the meta-data, so you will be able to see if it is even attempting to work or not, and if so, potentially if it is running into any problems. You ...


2

There are various possibilities and I will try to answer them according to the numbered questions. Valid connection strings for the SSMS login box are: 1st instance Using the host name SERVERNAME SERVERNAME,1433 Using the CNAME/Alias SERVERNAME-I01 SERVERNAME-I01,1433 Using the IP address 123.1.2.3 123.1.2.3,1433 For the Dedicated Admin ...


2

Since this is not a fully released version yet, I'd recommend opening a Microsoft Connect for this issue to make sure it gets addressed (I couldn't find a similar one myself after a bit of searching). I'm not sure that it's within the scope of DBA.se to troubleshoot release candidate software issues. I'd probably stick with SSMS 2014 until 2016 is fully ...


2

It turns out that it was indeed a bug that was squashed with the release of RC2 on 4/4/16. It had been occurring since the October preview, and I appreciate everyone's time and attention.


1

It looks like you have only installed SQL Server Management Studio (SSMS), and not SQL Server. SSMS is the tool used to connect to and manage SQL Server Instances, if you haven't installed a SQL Server instance you have nothing to run your queries against! Press Windows Key + R (Run) and type services.msc, check to see if the 'SQL Server' appears and that ...


1

I too was experiencing a 5 to 10 second delay when right-clicking a table to pull up the context menu. My situation might be a little different than some however because I use local databases only. My solution: After reading the answer from imran about disabling antivirus, I took that concept a step further since I do not want to disable my antivirus ...



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