<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:pingback="http://madskills.com/public/xml/rss/module/pingback/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>LifeCycle Solutions, LLC - Weblog - SQL Server</title>
    <link>http://blog.lifecycle-solutions.com/</link>
    <description>Technical Writing</description>
    <language>en-us</language>
    <copyright>LifeCycle Solutions, LLC</copyright>
    <lastBuildDate>Wed, 23 Aug 2006 21:35:02 GMT</lastBuildDate>
    <generator>newtelligence dasBlog 2.2.8279.16125</generator>
    <managingEditor>info@lifecycle-solutions.com</managingEditor>
    <webMaster>info@lifecycle-solutions.com</webMaster>
    <item>
      <trackback:ping>http://blog.lifecycle-solutions.com/Trackback.aspx?guid=08675cbd-8644-4e40-a9d9-0fdb20187e51</trackback:ping>
      <pingback:server>http://blog.lifecycle-solutions.com/pingback.aspx</pingback:server>
      <pingback:target>http://blog.lifecycle-solutions.com/PermaLink,guid,08675cbd-8644-4e40-a9d9-0fdb20187e51.aspx</pingback:target>
      <dc:creator>Brian Parks</dc:creator>
      <wfw:comment>http://blog.lifecycle-solutions.com/CommentView,guid,08675cbd-8644-4e40-a9d9-0fdb20187e51.aspx</wfw:comment>
      <wfw:commentRss>http://blog.lifecycle-solutions.com/SyndicationService.asmx/GetEntryCommentsRss?guid=08675cbd-8644-4e40-a9d9-0fdb20187e51</wfw:commentRss>
      <body xmlns="http://www.w3.org/1999/xhtml">Referencing fully-qualified object names
in SQL Server can be tedious, particularly if you're not using an editor with Intellisense
(a la <a href="http://www.apexsql.com/sql_tools_edit.asp">ApexSQL Edit</a>). 
If the object you're working with is on a linked server, it becomes even more of a
burden to get the full name correct, since it can have 4 parts:  <font face="Courier New">server.database.owner.object<br /></font><br />
Fortunately, SQL Server 2005 comes to the rescue with a new database feature called <i>synonyms</i>. 
Synonyms can be used as an alias to a fully-qualified object name, so the table "ProductionServer.ProductionDatabase.dbo.Parts"
can be referenced in your queries as simply "Parts" by issuing the following statement:<br /><br /><font face="Courier New">CREATE SYNONYM Parts for ProductionServer.ProductionDatabase.dbo.Parts</font><br /><br /><font face="Courier New">SELECT * FROM Parts</font><br /><br />
This can also be done visually in SQL Server Management Studio.<img width="0" height="0" src="http://blog.lifecycle-solutions.com/aggbug.ashx?id=08675cbd-8644-4e40-a9d9-0fdb20187e51" /></body>
      <title>Synonyms in SQL Server 2005</title>
      <guid isPermaLink="false">http://blog.lifecycle-solutions.com/PermaLink,guid,08675cbd-8644-4e40-a9d9-0fdb20187e51.aspx</guid>
      <link>http://blog.lifecycle-solutions.com/2006/08/23/SynonymsInSQLServer2005.aspx</link>
      <pubDate>Wed, 23 Aug 2006 21:35:02 GMT</pubDate>
      <description>Referencing fully-qualified object names in SQL Server can be tedious, particularly if you're not using an editor with Intellisense (a la &lt;a href="http://www.apexsql.com/sql_tools_edit.asp"&gt;ApexSQL
Edit&lt;/a&gt;).&amp;nbsp; If the object you're working with is on a linked server, it becomes
even more of a burden to get the full name correct, since it can have 4 parts:&amp;nbsp; &lt;font face="Courier New"&gt;server.database.owner.object&lt;br&gt;
&lt;/font&gt;
&lt;br&gt;
Fortunately, SQL Server 2005 comes to the rescue with a new database feature called &lt;i&gt;synonyms&lt;/i&gt;.&amp;nbsp;
Synonyms can be used as an alias to a fully-qualified object name, so the table "ProductionServer.ProductionDatabase.dbo.Parts"
can be referenced in your queries as simply "Parts" by issuing the following statement:&lt;br&gt;
&lt;br&gt;
&lt;font face="Courier New"&gt;CREATE SYNONYM Parts for ProductionServer.ProductionDatabase.dbo.Parts&lt;/font&gt; 
&lt;br&gt;
&lt;br&gt;
&lt;font face="Courier New"&gt;SELECT * FROM Parts&lt;/font&gt;
&lt;br&gt;
&lt;br&gt;
This can also be done visually in SQL Server Management Studio.&lt;img width="0" height="0" src="http://blog.lifecycle-solutions.com/aggbug.ashx?id=08675cbd-8644-4e40-a9d9-0fdb20187e51" /&gt;</description>
      <comments>http://blog.lifecycle-solutions.com/CommentView,guid,08675cbd-8644-4e40-a9d9-0fdb20187e51.aspx</comments>
      <category>SQL Server</category>
    </item>
    <item>
      <trackback:ping>http://blog.lifecycle-solutions.com/Trackback.aspx?guid=3ae21371-60b8-44f9-8438-87513e84c47f</trackback:ping>
      <pingback:server>http://blog.lifecycle-solutions.com/pingback.aspx</pingback:server>
      <pingback:target>http://blog.lifecycle-solutions.com/PermaLink,guid,3ae21371-60b8-44f9-8438-87513e84c47f.aspx</pingback:target>
      <dc:creator>Brian Parks</dc:creator>
      <wfw:comment>http://blog.lifecycle-solutions.com/CommentView,guid,3ae21371-60b8-44f9-8438-87513e84c47f.aspx</wfw:comment>
      <wfw:commentRss>http://blog.lifecycle-solutions.com/SyndicationService.asmx/GetEntryCommentsRss?guid=3ae21371-60b8-44f9-8438-87513e84c47f</wfw:commentRss>
      <title>SQL Server Report Builder</title>
      <guid isPermaLink="false">http://blog.lifecycle-solutions.com/PermaLink,guid,3ae21371-60b8-44f9-8438-87513e84c47f.aspx</guid>
      <link>http://blog.lifecycle-solutions.com/2006/07/20/SQLServerReportBuilder.aspx</link>
      <pubDate>Thu, 20 Jul 2006 20:59:46 GMT</pubDate>
      <description>&lt;div class="Section1"&gt;
&lt;p class="MsoNormal"&gt;
&lt;font face="Verdana" size="1"&gt;&lt;span style="font-size: 9pt; font-family: Verdana;"&gt;One
of the interesting features of SQL Server 2005 is a new utility for working with Reporting
Services called &lt;b&gt;&lt;span style="font-weight: bold;"&gt;&lt;a title="http://www.devx.com/dbzone/Article/28047/0/page/1" href="http://www.devx.com/dbzone/Article/28047/0/page/1"&gt;Report
Builder&lt;/a&gt;.&amp;nbsp; &lt;/span&gt;&lt;/b&gt;Designed as a reporting solution for the non-developer
set (a la MS Access reporting, and others), the tool works against “Data Source Views”
(DSVs) created as an abstraction of the underlying tables – the general idea is that
the end user works with entities and relationships of entities rather than with relational
database tables (think “General Ledger View” vs. GL00100, GL00101, etc.)&lt;o:p&gt;&lt;/o:p&gt;
&lt;/span&gt;&lt;/font&gt;
&lt;/p&gt;
&lt;p class="MsoNormal"&gt;
&lt;font face="Verdana" size="1"&gt;&lt;span style="font-size: 9pt; font-family: Verdana;"&gt;For
the more savvy users in some organizations, Report Builder, used in conjunction with
well-planned DSVs could eliminate some of the ad-hoc reporting tasks that are often
delegated to developers.&lt;o:p&gt;&lt;/o:p&gt;
&lt;/span&gt;&lt;/font&gt;
&lt;/p&gt;
&lt;p class="MsoNormal"&gt;
&lt;font face="Verdana" size="1"&gt;&lt;span style="font-size: 9pt; font-family: Verdana;"&gt;
&lt;o:p&gt;&lt;/o:p&gt;
Video demonstration &lt;a title="http://www.microsoft.com/sql/2005/bi/BIn_Ad-HocReporting500k.wvx" href="http://www.microsoft.com/sql/2005/bi/BIn_Ad-HocReporting500k.wvx"&gt;here&lt;/a&gt;.&lt;o:p&gt;&lt;/o:p&gt;
&lt;/span&gt;&lt;/font&gt;
&lt;/p&gt;
&lt;/div&gt;
&lt;p&gt;
&lt;/p&gt;
&lt;img width="0" height="0" src="http://blog.lifecycle-solutions.com/aggbug.ashx?id=3ae21371-60b8-44f9-8438-87513e84c47f" /&gt;</description>
      <comments>http://blog.lifecycle-solutions.com/CommentView,guid,3ae21371-60b8-44f9-8438-87513e84c47f.aspx</comments>
      <category>SQL Server</category>
    </item>
  </channel>
</rss>