sp_ExecVBScript allows you to execute either a .vbs file or an ad-hoc VBScript command within a T-SQL batch. Note that the command (whether it be ad-hoc or contained in the .vbs file) cannot have any code that requires user input (such as Input Boxes or Message Boxes).
2003-11-05
7,636 reads
New Author! This is a great article, seems like it covers almost every question you might have about installing and using the 64 bit version of SQL2K.
2003-10-31
9,981 reads
This script will join a single selected column from a select statement into a varchar variable. This works similarly to the javascript join function with a few additional features. By default the values will be joined with commas unless an alternate delimiter is supplied. The user can specify if the delimited values should quoted. To […]
2003-10-30
523 reads
This script Notifies the user(s) whenever there is an Error logged in the Error message. It excludes the Error messages 15457 and 1073759806. These 2 Errors can be ignored. (I know we like to keep our Elogs clean but for some time you need to yield to them J ). You’ll see the first error […]
2003-10-30
1,205 reads
New Author! This is a great walkthrough that starts out with a description of the problem and goes all the way to the solution - all using TSQL.
2003-10-30
12,137 reads
This script allows for testing if rows will cause a primary key violations prior to inserting the data. Offending rows are stored in a table so they can be used in subsequent queries or used to debug bad data issues. This updated version adds a timestamp to the duplicates table so that identifying when the […]
2003-10-28
1,825 reads
New Author! Ramesh talks a little about database theory, using the ERD, and how you can put it to work.
2003-10-28
22,471 reads
This function lists the column name and column id for primary key columns for a given table.
2003-10-24
1,533 reads
Sound like old hat ... but this procedure accepts the two database names as input parameters; therefore, it must dynamically generate the SQL and use Exec(@command) to execute it. It also reports on tables that exist in one database but not the other ... Finally, it uses count(*) to provide more accuracy than using sysindex […]
2003-10-24
295 reads
This articles proposes storing the source code for stored procedures on disk rather than in the database itself, the intent to give developers the ability to easily change them or potentially to allow third party encryption of source code. (Note from SSC: If you choose to implement a technique like this, please be sure you understand the implications of exec'ing strings)
2003-10-24
8,304 reads
By Chris Yates
The New Arena of Leadership The role of the Chief Data Officer is no...
Presenting you with an updated version of our sp_snapshot procedure, allowing you to easily...
SELECT * feels convenient, but in SQL Server it bloats I/O, burns network bandwidth,...
I've noticed several instances of what looks like a recursive insert with the format:...
Comments posted to this topic are about the item Cleaning Up the Cloud
Comments posted to this topic are about the item The Maximum Value in the...
I have a table with this data:
TravelLogID CityID StartDate EndDate 1 1 2025-01-01 2025-01-06 2 2 2025-01-01 2025-01-06 3 3 2025-01-01 2025-01-06 4 4 2025-01-01 2025-01-06 5 5 2025-01-01 2025-01-06I run this code:
SELECT IDENT_CURRENT('TravelLog')
I get the value 5 back. Now I do this:
SET IDENTITY_INSERT dbo.TravelLog ON
INSERT dbo.TravelLog
(
TravelLogID,
CityID,
StartDate,
EndDate
)
VALUES
(25, 5, '2025-09-12', '2025-09-17')
SET IDENTITY_INSERT dbo.TravelLog OFF
I now run this code.
DBCC CHECKIDENT(TravelLog)
GO
INSERT dbo.TravelLog
(
CityID,
StartDate,
EndDate
)
VALUES
(4, '2025-10-14', '2025-10-17')
GO
What is the value for TravelLogID for the row I inserted for CityID 4 and dates starting on 14 Oct 2025?
See possible answers