sqlspade Discussions Rss Feed

New Post: Powershell v3

sarasotasql — Thu, 20 Dec 2012 17:43:31 GMT

Josh,

Thanks for the great feedback. I believe that I have identified all of places where the "Control cannot leave a finally block" is occurring. I'm in the process of rebuilding my testing environment on new storage and as soon as that is complete I will test and upload the changes.

If you would like a list of the changes prior to that, please let me know and I'll email them to you.

Michael

New Post: Powershell v3

yardbirdsax — Fri, 07 Dec 2012 20:15:59 GMT

Hi there,

I am trying to use SQLSPADE on Windows Server Core 2012, and am getting some errors like "Control cannot leave a finally block". Looking around it appears to be a breaking change with Powershell v3. I would be happy to help fix this if it's not currently on your radar already.

Thanks for the great product. This thing has saved me many, MANY hours in standing up SQL server instances.

-Josh

New Post: TEMPDB data/log file location

sarasotasql — Wed, 08 Aug 2012 23:59:21 GMT

Thank you for catching that. For versions 2005-2008R2 the tempdb files are placed in the same location as the other system databases, and I neglected to make the adjustment for 2012 when they enabled the option to assign tempdb seperately.

My intended way of handling this is to either add the elements to the Run-Install.config file (if this is your standard) or adding the options to the $overrides hashtable (if this is a "one-off" build). The configuration ini files should not be updated as they are intended to be generic, and can be easily overridden using the methods we just discussed.

As an answer to your initial question, our standard is to locate the tempdb file with the rest of the system databases. The system databases generally don't have sufficient activity to interfere with tempdb.

I hope this answers your questions, if not I'd be happy to discuss this with you further.

Michael

New Post: TEMPDB data/log file location

brenbart — Wed, 08 Aug 2012 21:21:51 GMT

Or maybe just adding this to the Start-SqlSpade.ps1 file in the #Optional values section:

$overrides.Add("SQLTEMPDBDIR", 'T:\mssql\data')
$overrides.Add("SQLTEMPDBLOGDIR", 'T:\mssql\data')

New Post: TEMPDB data/log file location

brenbart — Wed, 08 Aug 2012 19:57:45 GMT

I see that by default the installer puts the tempdb files Root Install Directory.

Is this your typical configuration?

Over the years when I attempted to get the OS, datafiles, logfiles and tempdb on separate physical arrays the response from the sysadmin group ranged from laughter to outright refusal. (<scowl> "No, you get one RAID 5 array.")

In the past I've either left it on the drive with the Root install or moved the tempdb data/log files to the respective user DB data/log directory.

We have now virtualized all of our SQL servers and learned very quickly that you need to treat the LUNs as though they were normal drives/arrays. ( If we added two LUNs from the same VM drive pool it had the same effect as if they were two partitions sitting on the same physical drive.) This now puts me in the position where the sysadmin's don't scream if I say I want these multiple drives mapped to different drive pools. (They don't care since it's not physical disks.) So, I will be able to see if having the tempdb on a separate drive will make any noticeable difference.

I want to change the location of the tempdb data and log files in the SPADE install and had some questions...

Could I just add it to the template override setting in the Run-Install.config file?

.
.
.
<SqlVersions>
    <TemplateOverrides>
          <Setting Name="SQLTEMPDBDIR" Value="Physical Path" />
          <Setting Name="SQLTEMPDBLOGDIR" Value="Physical Path" />
   </TemplateOverrides>
</Version>
</SqlVersions>
</InstallerConfig>

Or do I need to add this to the configuration_<ver>.ini file:

SQLTEMPDBDIR=""
SQLTEMPDBLOGDIR=""

If the configuration_<ver>.ini entries are needed what should their values be?
   Blank?
   <Root Directory>\Data?
   $SystemDataDir?

New Post: Spade Helper Utility - Script Manager suggestions

brenbart — Tue, 24 Jul 2012 16:33:03 GMT

Thanks, that clears it up.

No apologies necessary. It's very difficult to see what will confuse others and if you try to explain every little thing your "simple" explanation will end up being the length of a book.

New Post: Spade Helper Utility - Script Manager suggestions

sarasotasql — Tue, 24 Jul 2012 16:04:36 GMT

There is no need to define an x86 or x64 path for 2008 and above becuase all of the architectures are on the same media. The setup.exe runs from the root of the media and based on the architecture of the system it choses the correct set of binaries.

The only reason that I have them separate for 2005 is becuase the x86 and x64 installs were on different sets of discs and therefore needed to be placed in separate folders for SPADE.

That being said, your nodes for 2008, 2008R2, and 2012 should look similar to this...

I hope this answers your question and I apologize for any confusion.

New Post: Spade Helper Utility - Script Manager suggestions

brenbart — Tue, 24 Jul 2012 15:23:34 GMT

Given this snippet of the run-install.config file what should the install folder for the 32 and 64 bit folders look like?

<DataCenters>
    
    <DataCenter Name="Data Center 1" Location="Location 1" FilePath="B:\install\" />
</DataCenters>
<SqlVersions>
      <Version Name="SQL2008R2">
      <ConfigurationTemplate Name="Configuration_2008R2.ini" Category="SQLSERVER2008" />
      <ProductStrings>
        <ProductString Name="Default" Value="SQLENGINE,REPLICATION,FULLTEXT,CONN,BC,SSMS,ADV_SSMS,BOL" />
        <ProductString Name="DefaultPlusIS" Value="SQLENGINE,REPLICATION,FULLTEXT,BIDS,CONN,IS,BC,SSMS,ADV_SSMS" />
        <ProductString Name="Minimal" Value="SQLENGINE,CONN,BC,SSMS,ADV_SSMS" />
      </ProductStrings>
      <Editions>
        <Edition Name="Enterprise_32" Key="" FolderName="SQL2008R2\Enterprise\32" />
        <Edition Name="Enterprise_64" Key="" FolderName="SQL2008R2\Enterprise\64" />


Below is a rough approximation of the install CD file structure.

When I run the SpadeHelper/spade folder builder It puts the contents of the appropriate x64 or x86 folders under "SQL2008R2\Enterprise\64" or "SQL2008R2\Enterprise\32" but when I try to run the install script it's looking in that 32/64 folder for the setup.exe from the root of the CD. I tried changing the name to setup100.exe but it wouldn't run properly because it was looking for something done by the root setup.exe.

Do the 32/64 bit folders need to have everything at the root of the CD but with certain subfolders excluded? i.e. for the 64bit install essentially have the entire cd minus the x86 folder?

Why even have seperate media locations for the installs, why not just a copy of the entire install?


     CD_Root
         1033_ENU_LP
         ia64
         MasterDataServices
         redist
         resources
         StreamInsight
         autorun.inf
         MediaInfo.xml
         Microsoft.VC80.CRT.manifest
         msvcr80.dll
         setup.exe
         setup.exe.config
         sqmapi.dll
         x64
             setup100.exe
             <various x64 specific files and folders>
         x86
             setup100.exe
             <various x86 specific files and folders>

New Post: Spade Helper Utility - Script Manager suggestions

brenbart — Tue, 17 Jul 2012 17:08:17 GMT

New Post: Spade Helper Utility - Script Manager suggestions

sarasotasql — Thu, 12 Jul 2012 22:50:04 GMT

You have a good point, adding the script name doesn't help if the full path doesn't fit. Besides, the path is already on the top of the window anyways.

So I changed the code to only show the script name and moved the full path to a tooltip that appears if you mouse over the script name.

Have you been able to build the auto install folders yet?

New Post: Spade Helper Utility - Script Manager suggestions

brenbart — Thu, 12 Jul 2012 17:47:37 GMT

I tested the changes you made to the script manager and the folder builder and they worked as advertised.

The only suggestion I'd make is that maybe the status bar at the bottom in the script manager only display the file name not the full path. I happened to be testing with a long convoluted path and was unable to read the actual file name because it extended past the window dimensions.

Then again, the path info is helpful so it's probably fine the way it is.

New Post: Spade Helper Utility - Script Manager suggestions

brenbart — Wed, 11 Jul 2012 03:12:24 GMT

Absolutely. I will probably have a chance to check on it this week.

From: sarasotasql [email removed]
Sent: Tuesday, July 10, 2012 10:45 PM
To: Bartlett, Brendan
Subject: Re: Spade Helper Utility - Script Manager suggestions [sqlspade:362695]

From: sarasotasql

I have addressed your suggestions by making the following changes:

1) I added a status bar to the bottom of the script window that shows the current script file

2) I fixed the Save button so that when you save the script it resets the save status and clears the save button

3) Added the Config file to the left hand navigation so that you can edit the Run-Install.config file - I would eventually like to add a cleaner editor so that you don't need to edit the XML by hand, but that will take a bit more time.

I also added a close button that appears when you open a script for editing.

Would you be willing to test these changes and provide any additional feedback? The changeset can be downloaded from http://sqlspade.codeplex.com/SourceControl/changeset/changes/4c5c7e112767.

Confidentiality Notice: This transmission may contain information that is privileged, confidential, legally privileged, and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is strictly prohibited. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you.

New Post: Spade Helper Utility - Script Manager suggestions

sarasotasql — Wed, 11 Jul 2012 02:44:56 GMT

I have addressed your suggestions by making the following changes:

1) I added a status bar to the bottom of the script window that shows the current script file

2) I fixed the Save button so that when you save the script it resets the save status and clears the save button

I also added a close button that appears when you open a script for editing.

Would you be willing to test these changes and provide any additional feedback? The changeset can be downloaded from http://sqlspade.codeplex.com/SourceControl/changeset/changes/4c5c7e112767.

New Post: Spade Helper Utility - Script Manager suggestions

brenbart — Tue, 10 Jul 2012 16:42:38 GMT

Just a few suggestions after using the Script Manager...

If I double-click on a script it opens in the detail window to the right but the name of the script being actively edited is not displayed anywhere that I can see. Maybe put it in the window bar or keep it highlighted in the tree frame on the left?

The 'save' button does not visibly do anything after making changes to a script. However, when you go to another script you are asked whether it should save your changes. I haven't tested whether the button actually saves things or not but my usual expectation for this type of application would be that the 'save' button is grayed out until you make changes and then after clicking the button to save it goes gray again until further changes are made. (I expect this type of fix has a relatively low ROI since it works ok the way it is but thought I'd throw it out there.)

Not sure how you'd do it but a way to edit a selected script's parameters that go in the Run-Install.config file would be helpful. Maybe a button to push the parameters to the Run-Install.config file? Or a separate popup window that displays the xml entries that should be in the config file where you can copy them for pasting into the config file?

Allow the Run-Install.config to be edited in the script manager?

New Post: SqlSpadeHelper - Unhandled exception Error trying to select source files.

brenbart — Tue, 10 Jul 2012 14:29:15 GMT

Thanks for getting back to me so quickly!

It encourages me to be a more active participant online and with open source projects since I tend to be a lurker.

I was also about to give up on sqlspade and just go back to a manual install.

(You are also providing a valuable distraction from a large boring meeting.)

I have a few other questions regarding the general structure of spade but I will post them later today.

From: sarasotasql [email removed]
Sent: Tuesday, July 10, 2012 08:32 AM
To: Bartlett, Brendan
Subject: Re: SqlSpadeHelper - Unhandled exception Error trying to select source files. [sqlspade:362548]

From: sarasotasql

Thank you for taking the time to report this issue. With the information that you provided I was able to identify the bug and make the needed correction.

I will be including the updated code in the next release, but you can download it from the following link now - http://sqlspade.codeplex.com/SourceControl/changeset/changes/1e9ba629d7dd. When you use the download option on the page, it will download a zip file that contains all of the latest code. Since there may be other changes since the last release, I recommend that you pull only the SqlSpadeHelper.exe from the zip file.

There is also a workaround for the version you have now, which is to select the action from the list, even if it appears to already be selected.

I apologize for the inconvenience and welcome any additional feedback that you have.

New Post: SqlSpadeHelper - Unhandled exception Error trying to select source files.

sarasotasql — Tue, 10 Jul 2012 12:32:33 GMT

Thank you for taking the time to report this issue. With the information that you provided I was able to identify the bug and make the needed correction.

There is also a workaround for the version you have now, which is to select the action from the list, even if it appears to already be selected.

I apologize for the inconvenience and welcome any additional feedback that you have.

New Post: SqlSpadeHelper - Unhandled exception Error trying to select source files.

sarasotasql — Tue, 10 Jul 2012 12:05:03 GMT

This discussion has been copied to a work item. Click here to go to the work item and continue the discussion.

New Post: SqlSpadeHelper - Unhandled exception Error trying to select source files.

brenbart — Mon, 09 Jul 2012 15:40:28 GMT

I run SQLSpadeHelper, select a config file, data center, check, build the folders then click on edition line to bring up detail window.

The action is populate folder and no matter what I pick for either an iso file or a folder when I click 'ok' I get the generic error below and the program goes no further.

I am running this on a Win Server 2008 R2 and have tried on a Win XP workstation as well. (running current downloaded version of SPADE.)

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
   at SqlSpadeHelper.frmFolderBuilderDetail.btnOk_Click(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Loaded Assemblies **************
mscorlib
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.269 (RTMGDR.030319-2600)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
SqlSpadeHelper
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///B:/install/SPADE/Tools/SqlSpadeHelper.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.278 built by: RTMGDR
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.282 built by: RTMGDR
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.269 built by: RTMGDR
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Xml
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.233 built by: RTMGDR
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

New Post: service packs

sarasotasql — Tue, 26 Jun 2012 17:39:35 GMT

SQL SPADE doesn't currently support upgrading or applying service packs to existing installations. It does however support the use of Slipstream installation media when installing new instances. Details of creating a Slipstream install of SQL 2008/R2 can be found here: http://msdn.microsoft.com/en-us/library/dd638062(v=sql.105).aspx.

Thank you for your feedback.

New Post: service packs

pkeisler — Sat, 16 Jun 2012 14:28:29 GMT

SQL Server 2008 supports slipstream installation, so maybe you could build your install files as slipstreams.