I have several objects, all in the same schema. Because of this, ownership chaining is working, as described in this previous tip. However, I don't want ownership chaining to be on, but I need the objects to remain in the same schema. How can I do this?
2009-08-21
3,302 reads
Part three of this series illustrates how to use a T-SQL script to create database mirroring between a principal and mirrored server.
2009-08-20
3,401 reads
A main function of SQL Server Integration Service is to move data into and out of SQL Server. The external data source can exist in almost any format, including a plain text file. This article focuses on importing a text file into a standard SQL Server database table.
2009-08-20
4,444 reads
Creating a private SQL Server VAP will reduce the time it takes to deploy additional SQL Server machines in your environment.
2009-08-19
3,498 reads
One could be forgiven for thinking that there's little more you can do with third-party backup software than just ...er... backup databases. Shawn McGehee gives us his personal take on the implications of the improvements that have been made to SQL Backup for version 6.
2009-08-19
2,436 reads
Disk partition alignment is a powerful tool for improving SQL Server performance. Configuring optimal disk performance is often viewed as much art as science. A best practice that is essential yet often overlooked is disk partition alignment. Windows Server 2008 attempts to align new partitions out-of-the-box, yet disk partition alignment remains a relevant technology for partitions created on prior versions of Windows.
2009-08-18
3,407 reads
Everything I've read about the built-in configuration options is that you can retrieve values from a SQL Server table, an XML file, etc. but I really prefer to just use the command line options. I'm currently specifying 10 or more command line options on average. Do you have any ideas on a better way to do this?
2009-08-18
3,212 reads
In a previous tip, Granting limited permissions to create views in another schema in SQL Server, I showed how to use the CREATE VIEW permission and the ALTER SCHEMA permission to allow users to create new views using the same schema as the tables. However, I have found that the users can alter and drop tables in this schema which is beyond what I want them to do. A DENY CREATE TABLE does not work, so what can I do to prevent them from touching the tables in this way? In this tip I will show you how you can use a DDL trigger to prevent this unneeded access.
2009-08-17
3,444 reads
SharePoint administrators can minimize data loss by selecting the appropriate SQL Server recovery model. But which model is right for your enterprise?
2009-08-17
4,000 reads
Examining what has already occurred, while valuable in some cases is most likely not as important as what is currently taxing your server. This being the case, how do you examine the currently executing statement for each of the requests issued against your SQL Server instance?
2009-08-14
4,448 reads
By Brian Kelley
There's a great article from MIT Technology Review about resetting on the hype of...
By Steve Jones
etherness – n. the wistful feeling of looking around a gathering of loved ones,...
By Steve Jones
A customer was asking about tracking logins and logouts in Redgate Monitor. We don’t...
Comments posted to this topic are about the item The Max PK Length
Comments posted to this topic are about the item My experience using the GitHub...
Comments posted to this topic are about the item The Microsoft SQL Year in...
If I create a multiple column Primary Key constraint, what is the most number of bytes I can include in the constraint?
See possible answers