|
|
|
SSCrazy
      
Group: General Forum Members
Last Login: 2 days ago @ 8:46 AM
Points: 2,750,
Visits: 1,410
|
|
|
|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: Monday, March 08, 2010 5:04 AM
Points: 135,
Visits: 90
|
|
Are there any plans to be able to specify a team repository for templates in SS 2008?
We had to implement a similar solution as outlined in the article which works fine but it would be great to not have to run a batch script.
-- JP
|
|
|
|
|
Valued Member
      
Group: General Forum Members
Last Login: Thursday, February 16, 2012 7:34 PM
Points: 59,
Visits: 375
|
|
Looks like the editor "ate" most of your code blocks. 
What does the XCOPY command look like?
|
|
|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: Wednesday, February 04, 2009 1:49 PM
Points: 160,
Visits: 140
|
|
|
|
|
|
SSCrazy
      
Group: General Forum Members
Last Login: 2 days ago @ 8:46 AM
Points: 2,750,
Visits: 1,410
|
|
CAGreensfelder (5/20/2008)
Looks like the editor "ate" most of your code blocks.  What does the XCOPY command look like?
What browser are you using? In FireFox the code block gets a scrolling window.
LinkedIn Profile
|
|
|
|
|
Valued Member
      
Group: General Forum Members
Last Login: Thursday, February 16, 2012 7:34 PM
Points: 59,
Visits: 375
|
|
I'm using IE7 on WinXP Pro 2002 SP2, all patches applied. Over half the code blocks in this article come up as a horizontal scroll bar only - no vertical. This happens occasionally. Guess I should report it to webmaster when it happens. They can't fix it if no one tell 'em it's broke.
I looked at the page source and found the bits I was interested in.
We use SQLMS with Visual SourceSafe. We've got 3 developers each working with thier own local dev SQL server. We wrote templates for the CRUD stored procedures and a few other tools with our shop headers and standard error handling.
We have separate SQLSM projects for different areas of the application in the SQLMS solution and we included a project for the templates. But rolling out the templates to the actual template folder has been a pain - that's one LONG path. (We finally stuck a text file in the Templates project with the template file path name so we could remember it. It shows up in the Misc folder in the project)
Now I've got a batch file in the project to XCOPY the templates. Much easier to just double-click the batch and let it remember where the templates go.
|
|
|
|
|
SSCarpal Tunnel
       
Group: General Forum Members
Last Login: Wednesday, May 22, 2013 1:35 AM
Points: 4,789,
Visits: 1,336
|
|
|
|
|
|
SSC Veteran
      
Group: General Forum Members
Last Login: Wednesday, March 11, 2009 8:20 AM
Points: 269,
Visits: 1,093
|
|
Good article. I have used the templates, but I like your method of getting team templates distributed.
CAGreensfelder - I have a similar setup as you and the code blocks don't show right either. I've found you can highlight the block, copy it and paste into something like notepad. The text will show up then. It seems to happen when there is just one line in the block.
Ian.
"If you are going through hell, keep going." -- Winston Churchill
|
|
|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Friday, January 04, 2013 8:32 AM
Points: 2,
Visits: 8
|
|
You can customize your templates by following the following advice. Using this method you would be able to get rid of the unused templates and create new ones suitable to your profession that can be shared.
Steven Twitchel from MSFT wrote in another forum on October 13, 2006
Management Studio was designed with multi-user environments in mind. When SSMS starts, it checks a "common template folder" for templates and if any template is missing in a user's folder, it is copied from the common location. This lets an administrator add a template to a common location and all the users on the machine will automatically get a copy when they start SSMS.
If you want to permanently remove a template, first delete the file from ...\Documents and Settings\{user}\Application Data\Microsoft\Microsoft SQL Server\90\Tools\Shell\Templates\... (this removes the user's private copy), then remove the common template from %ProgramFiles%\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\sqlworkbenchprojectitems. Once the common version has been removed, SSMS won't be able to copy it to the user's template directory during application startup.
This works in SSMS 2008 using: \Documents and Settings\{username}\Application Data\Microsoft\Microsoft SQL Server\100\Tools\Shell\Templates\Sql – for the private copy
%Program Files%\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\SqlWorkbenchProjectItems\Sql – for the common version
|
|
|
|
|
Valued Member
      
Group: General Forum Members
Last Login: Thursday, February 16, 2012 7:34 PM
Points: 59,
Visits: 375
|
|
| Do you have a link to the article? I'm not finding anything on my searches.
|
|
|
|