I suspect that any developer who has been near a SQL Server for more than just a short while, you will be able to recognize a list of SQL Agent jobs that can no longer can be seen in its full extent without having to scroll.
A tip to make it easier for yourself is that you can filter the list.
Just right-click ‘Jobs’ and select Filter->Filter Settings and you’re off.
Then punch in the filtering you’d like to have
And voila, your list of jobs are filtere to show only the ones you want:
Having to install new laptops, re-install old ones, configuring virtual servers or whenever you get the opportunity to install SQL Server from scratch, you always end up with an empty list of servers, when you try to connect through SQL Server Management Studio (SSMS).
There is a way around this minor, but still sometimes very annoying issue.
The information is stored in one file only, on the profile you are currently logged on to. So copying this file, from an existing setup or a shared repository (like SkyDrive or TFS), to the new environment will bring you up to speed really quick.
The file is named SqlStudio.bin and can be found at <DRIVE>:\Users\<PROFILE>\AppData\Roaming\Microsoft\SQL Server Management Studio\<SQLVersion>
Disclaimer:
I have not tested if any third-party tools register anything in this file, so beware and be sure to have the original file ready, in case of dissaster
Error: Cannot resolve the collation conflict between “Danish_Norwegian_CI_AS” and “SQL_Latin1_General_CP1_CI_AS” in the UNION operation. (Microsoft SQL Server, Error: 468) when clicking “Securables” in properties of a server login.
Server is set up with collation: SQL_Latin1_General_CP1_CI_AS
The database, or more precisely, the columns are created with collation: Danish_Norwegian_CI_AS
Login is set up with default language: English
The following steps will reproduce the error:
1. See properties for the server-login:
2. Click “User Mapping”
3. Click “Securables”
4. Observe error:
Cannot resolve the collation conflict between “Danish_Norwegian_CI_AS” and “SQL_Latin1_General_CP1_CI_AS” in the UNION operation. (Microsoft SQL Server, Error: 468)
Can anyone say anything intelligent about this issue?
If you ever need to test Analysis Services roles, you can easily do so either by browsing the cube or by means of a query.
When browsing a cube through SQL Server Management Studio (SSMS) or Bisuness Intelligence Developer Studio (BIDS), you can select one or more roles to be enforced on data, by clicking the little “user” icon in the top left corner of the cube browser:
You will then be able to select on or more of the roles available on the database via a dialog:
This way of browsing roles has the following pros and cons:
Pros: Visual confirmation of PC Hierarchies
Cons: A lot of clicking top verify permission integrity
The other way of testing roles is through SSMS is by creating an MDX query. The trick is to click the options button when the connection dialog is active. The last tab allows you to specify additional connection parameters. The Roles property is described in detail at technet. Basically it’s a comma seperated list of roles (case sensitive). The trick is showed in the screendump below:
Pros: Custom queries
Cons: No visual confirmation of integrity, can be hard to visually confirm permissions on a PC hierarchy as an example
Looking for some other settings I stumbled upon this very nice, and very hidden, feature in SQL Server Management Studio (SSMS): The ability to set your default column type!
That should save me a lot of time, from now on.