• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 368
  • Last Modified:

SQL Server Samples and Sample Databases

At this location; http://msdn.microsoft.com/en-us/library/ms161556(v=sql.105).aspx;
Considerations for Installing SQL Server Samples and Sample Databases

I find this;
Updating the Location for the .NET Framework CLR Samples
Before you compile Microsoft .NET Framework common language runtime (CLR) samples for SQL Server, verify that the path of the version of the .NET Framework compiler is the first Framework directory in the PATH environment variable. The location of the compiler that is shipped with this release of SQL Server is C:\<Windows root directory>\Microsoft.NET\Framework\v2.0.x. Drive C is the installation drive, <Windows root directory> is either Windows or WINNT, and x is five digits.

Question:  In my "system environment variable path" I do not see the path specified.  My questions are these; I have a "framework" and a framework64"  I believe that using framework64 is correct because that is my OS, and that is the SQL Management Studio that I installed.

While the instructions above state the path as being \v2.0.x, I have several versions.  Which path should I use?  I could set it to v2.0.x, but is this the best of my selections;
Framework 64
1 Solution
David ToddSenior DBACommented:

The path is usually easily fixed. So I'd go ahead with the samples and go back to the path if you need to use the CLR.

SQL will use a specific version of .net, so you will need to use that version of the framework - the instructions you mentioned said v2.0.xxxxx, so use that if needed.

Other versions of SQL may use a more recent version. (You didn't say and the page didn't either - which version of SQL are you looking at samples for?)

chimaAuthor Commented:
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now