DTS is a great tool in SQL Server 2000 for easily setting up jobs to import or export data. But it can also have security risks. New author Alex Kersha brings us a simple security technique to be sure that you are properly executing your DTS packages in a secure manner.
By default, SSIS files in development are encypted to prevent an unauthorized person from seeing your SSIS package. The type of encyrption is seamless behind the scene and is at a workstation and user level. So, if you were to send a package that you're developing to another developer on your team, he would not be able to open it by default. This shows you how to fix this problem.
Despite a growing range of options for integrating mixed database environments, some companies are sidestepping the problem by moving to a single database platform.
Apress is giving away some copies of this book on SQLServerCentral.com by sponsoring our Question of the Day. A sample chapter is also available online now!
Continuing with his series, Andy Warren looks at what it means for SQL Server 2000 command line parameters as well as checkpointing with this service.
In this lesson, we revisit Named Sets, a subject that we undertook in my article MDX in Analysis Services: Named Sets in MDX: An Introduction, in March of 2004. There, we introduced Named Sets from the perspective of the MDX query language, having obtained brief exposure to the concept of Named Sets earlier in the MDX in Analysis Services series (Using Sets in MDX Queries). We examined Named Sets as they existed within Analysis Services 2000, touching upon them from the perspective of Analysis Manager, the Cube Editor, and related interfaces in Analysis Services.
Steve Jones recently took the 70-441 Beta exam for Developing Solutions on SQL Server 2005. This article will not break the NDA and tell you what the content is, but it gives you some feedback from a SQL Server 2000 DBA on the new exam.
With the introduction of SQL Server 2005, Microsoft has created a new .NET management API for SQL Server called SQL Management Objects (SMO). As I started working with SQL Server in earnest following its release I discovered a few limitations that I hoped to correct using SMO. This article describes those problems and how to use SMO to script database objects.
A quick and dirty procedure to allow you to grant execute permissions to a user, or role, quickly and easily.
One of the many tasks of the SQL Server Database administrator is to take and maintain backups of SQL Server databases. This includes taking backups of analytical databases as well. Read on to learn how to backup an Analysis service database.
By DataOnWheels
I have been active in the data community throughout my career. I have met...
By Vinay Thakur
Quick Summary for Microsoft SQL Server till 2025, I am fortunate to be part...
By James Serra
Why this comparison feels confusing If you’re a Power BI report author who’s just...
Hello, Is there a way in Azure SQL Database to change the 'Blocking Process...
Comments posted to this topic are about the item Having a Little Fun at...
Comments posted to this topic are about the item Designing SQL Server Pipelines That...
On SQL Server 2025, when I run this, what is returned?
SELECT EDIT_DISTANCE_SIMILARITY('SQL Server', 'MySQL') See possible answers