-
Renamed sa causing problem during replication distribution setup
In a previous post, I mentioned that it may be a good security practice to rename sa to something else. However, if you did that and later on decided to make the server a distributor in replication, you will get the error message below: Cannot find the principal ‘sa’, because it does not exist or…
-
Find out version number of Reporting Services
Here is how to find out the version number of Sql Server Reporting Services on your machine: Go to http://MyServerName/ReportServer. The version number is listed at the bottom of the page, like this: Microsoft SQL Server Reporting Services Version 8.00.1038.00
-
Sql Server aliases can be handy at times
In both Sql Server 2000 and Sql Server 2005, you can create server aliases on your client machine. When you connect to the database server from this client, you can use the server’s alias, instead of its real name. This can be handy at times. For example, if you have a DTS / SSIS package…
-
DTS runtime and Legacy Components are not supported on 64-bit
SQL Server 2005 provides a utility called DTS Migration Wizard to help you move your legacy DTS 2000 packages to SSIS format. It is not guaranteed to work perfectly, but it will make a best-effort attempt. Initially, you may want to install DTS runtime on the SQL Server 2005 box so you can continue running…
-
Connect to a different database server within command line utility
In sqlcmd, you can connect to a different server by this command: :connect MyServer The above command will attempt to use integrated / Windows Active Directory authentication. To use traditional Sql Server authentication, use this instead: :connect MyServer -U MyLogin You can do the same kind of thing in Oracle Sql Plus by using this…