Jimmy'sTubeCast Blog

One of the many great things that make AutoStore so powerful is the Runtime Replacement Tag, better-known by its more familiar acronym as the RRT. These placeholders of information positioned inside the desired location of an AutoStore workflow configuration provide solution designers with the ability to simplify front-end business processes by connecting variable source values to create both well-structured and dynamic routes. Adding RRTs to a configuration is quick and simple. For a given component's configuration properties, set the mouse cursor, and from the list of available RRTs, drag-and-drop the desired RRT. For example, an RRT could variably define the email address that the Send to Mail Recipient should send the message to, or perhaps define all or part of a UNC path for the Send to Folder component to write the file over to. Most of the components in AutoStore have an RRT that show up in the list of available RRTs, as well as a description in its Help file. By mo

To preface what could be regarded as a very small thing, I am reminded of a common turn of phrase concerning the amount of perspiration that should be afforded to the "stuff" belonging to a particular size-category, and pretty sure there was a book written about that topic. Not to come across as disagreeable, but rather to invite a little balance based on my own general observations over time, an increase in cost with things such as time, money, even relationships, can be avoided when the "small stuff" is given the regard that it deserves. One of these tiny details has to do with string variables that reference folder paths within a script. There are times when it is important that a defined directory for a particular folder should and must always end with a backslash. As an example: folderPath = "C:\Example"   Of course, it really is not very difficult to manually enter that backslash into the path. folderPath = "C:\Example\"

When using SQL Server Management Studio, executing very large queries can bring up a message that the operation cannot be completed, and that there is not enough storage to process the command. An example of a large file would be a sql script that inserts thousands of records into a table. Rather than using the GUI, we can use Sqlcmd at the command line. Open a CMD Prompt as Administrator. There is no need to change to any specific directory in the CMD prompt. Enter the following, and press Enter: C:\>sqlcmd -S ServerName -d DataBaseName -i "FolderPath\FileName.sql" Run a SQL script from the command prompt -S indicates the name of the SQL Server instance -d indicates the name of the SQL database -i indicates the file path to the .sql input file For more information on available paramteters, enter: C:\>sqlcmd /? Enter sqlcmd /? for more information