Articles

SQLServerCentral Article

More Portable DTS Packages

There have been a few articles over time on how you can build DTS packages in SQL Server 2000 that are easily moved from one server to another. New author Tito David brings us another technique that not only migrates packages easily between servers, but between your development and production environments.

You rated this post out of 5. Change rating

2005-04-07

9,280 reads

Technical Article

SQL Server 2005 Editions and Integration Services

The SQL Server 2005 product family has now been announced, so with four editions available, what does this mean for SQL Server Integration Services? Starting from the bottom we have the free edition known as Express, and the entry level Workgroup edition, and neither include the full IS product. They have the Import/Export capabilities, but nothing more, so for simple loading and extraction of data this should suffice, but you will not be able to build packages.

2005-04-07

4,009 reads

SQLServerCentral Article

BDS SQL Digger 2.0 Released

Have you ever needed to find something in a stored procedure or function and found yourself trying to wade through syscomments? Ever want to know which views reference a table, but you don't trust sysdepends? BDS has released SQL Digger 2.0, a utility designed to help you search through your schema and code to find what you need.

4 (1)

You rated this post out of 5. Change rating

2005-04-05

3,779 reads

SQLServerCentral Article

Flexible DTS Packages with Perl

SQL Server 2000 DTS was a revolutionary programming environment, but one that was not without a few quirks. As often found with many Microsoft products, there were sections in your packages where things were hard coded, making them less flexible. New author Jeremy Brown brings us a look at how you can build extremely flexible packages using Perl.

You rated this post out of 5. Change rating

2005-04-05

11,032 reads

SQLServerCentral Article

Know Your Data

Or at least the types of your data. New author Roy Carlson was working in SQL Server 2000 to calculate some values based on row counts, sales amounts, etc. and discovered some interesting results. Without his sharp eye, a number of individuals would have been upset by the resulting lack of commissions, as may some of your clients. Read about some potential problems in your calculations if you are not careful with your data types.

You rated this post out of 5. Change rating

2005-04-04

6,656 reads

Blogs

Azure SQL offerings

By

There are three Azure SQL products with so many different deployment options, service tiers,...

T-SQL Tuesday #183 Roundup

By

I hosted this month’s T-SQL Tuesday party with my invitation asking about tracking permissions....

A Little Brainstorming with an AI

By

I was asked to do some a little thinking and brainstorming recently. Rather than...

Read the latest Blogs

Forums

MEMORYBROKER_FOR_RESERVE experience

By tony28

Hi, Does anyone have experience with MEMORYBROKER_FOR_RESERVE ? when suddenly there is somehow constantly...

Moving Database Files

By Ahr Aitch

I just learned that my database was created on my C:\ drive in the...

Migrate MSSQL to MYSQL - Different Servers

By cajun_sql

I am needing to migrate a MSSQL db to MySQL, on a different server...

Visit the forum

Question of the Day

Mixed Backups

I have a complex database with a few filegroups and files. Can I run a backup command like this? (assume file/filegroup names are valid).

BACKUP DATABASE [complex]
    FILE = N'thirdone'
 ,  FILE = N'thirdtwo'
 ,  FILEGROUP = N'second' 
 TO  DISK = N'C:\Program Files\Microsoft SQL Server\MSSQL16.SQL2022\MSSQL\Backup\complex.bak' 
 WITH NOFORMAT, NOINIT,  NAME = N'complex-Full Database Backup', SKIP, NOREWIND, NOUNLOAD,  STATS = 10
GO

See possible answers