One of the excellent features of the next release of SQL Server, known as SQL Server 2005, is its deep XML integration with the SQL Server database engine. This integration goes well beyond the simple relational-to-XML mapping layer that SQL Server 2000 provided. SQL Server 2005 will feature a native XML data type that will allow you to store native XML data in SQL Server itself.
Many programming languages have supported User Defined Functions for years, but they are new to SQL Server 2000. In this article we will look at some of the ways functions can be used within SQL Server 2000.
You can use features in Microsoft Office InfoPath 2003 Service Pack (SP) 1 to work more efficiently with image objects and other data. Learn how to use BLOB data types to work with data stored in a Microsoft SQL Server 2000 database from an InfoPath form. InfoPath 2003 provides a robust and rich interface to store and access data in SQL Server databases. Learn about best practices for integrating SQL Server databases and InfoPath form data, with an illustrative example.
How many times has an application exploded because you upgraded or patched SQL Server? How many people were aware that a patch was applied? New author Andre Vigneau has dealt with this and gives us some code that our applications can use to check to see if anything has changed. It doesn't keep the code working, but it does allow you to inform users that something has changed.
This is the twenty-fourth article of the series, MDX Essentials. The series is designed to provide hands-on application of the fundamentals of the Multidimensional Expressions (MDX) language, with each tutorial progressively adding features designed to meet specific real-world needs.
Version control in SQL Server is fairly immature, to put it nicely. Fortunately it's also an area that a number of vendors are working to make smoother. Dinesh Asanka looks at dbMaestro, a tool from Extreme Technologies to help you track changes in multiple databases.
This article examines how to take advantage of VB Script and MS-DOS batch files to restore multiple DTS packages stored in the form of structured storage files from one folder to a SQL Server box.
SQL Server has a rock solid backup routine that works every time. However the schemes used to implement backups with maintenance plans, Enterprise Manager, etc., are not a smooth or as flexible as what most people require. Author Eli Lieba brings us his strategy and code for ensuring that each database is backed up how he needs it to be, whether a full or differential backup.
Typically, access to data is provided via client applications, which increases the range of potential vulnerabilities and places an equal share of responsibility for data security on software developers. This is especially important since application flaws can have just as catastrophic implications as a misconfigured or unsecured SQL Server installation.
SQL Server's Data Transformation Services (DTS) is a fantastic tool for importing data from any type of source. However even with this tool, you sometimes need more flexibility than it appears to have, especially if the data formats are unknown far enough in advance. New author Chris Cathers has developed a technique that allows him to be extremely flexible without causing too many headaches down the road.
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