SQL Server 2000 has table valued functions that are very useful in many ways. However when you try to limit results with the ROWCOUNT setting, you can end up with some strange results. Peter He brings us a comprehensive look at some of the unpredictable results that you can get and how to code around them.
A few months ago, I posted an article here at DBJ named How to Pass Access Data Across the Web. One reader expressed concern over using the Microsoft Internet Explorer library because of security issues. While I do not share his fear, I appreciate that others might, so I began to think about how the process could be enhanced by substituting a Web Service for the traditional ASP/Querystring web page approach described in the article. What follows is the fruit of those labors.
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.
By HeyMo0sh
As someone who works in DevOps, I’m always focused on creating systems that are...
By Brian Kelley
I am guilty as charged. The quote was in reference to how people argue...
By Steve Jones
Learn how to tie a bowline knot. Practice in the dark. With one hand....
Comments posted to this topic are about the item Restoring On Top II
Comments posted to this topic are about the item SQL Art 2: St Patrick’s...
Comments posted to this topic are about the item Breaking Down Your Work
I have a database, DNRTest, that has a number of tables and other objects in it. The other day, I was trying to mock up a test and ran this code on the same server:
-- run yesterday CREATE DATABASE DNRTest2 GO USE DNRTest2 GO CREATE TABLE NewTable (id INT) GOToday, I realize that I need a copy of DNRTest for another mockup, and I run this:
-- run today USE Master BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO RESTORE DATABASE DNRTest2 FROM DISK = 'dnrtest.bak' WITH REPLACEWhat happens? See possible answers