SQL Server has this concept of an owner of an object. Similar to the concept of schema, but not quite the same. Best practice dictates that all objects in SQL Server be owned by dbo, but that does not always happen. Tracking those objects down might be a pain, but Santveer Singh brings us an easy way of doing this.
2004-12-15
6,093 reads
Learn how to achieve scalable, high-performance merge replication applications. (White Paper)
2004-12-15
1,751 reads
Destroyed your database? Corrupted files? What about corrupted records? What do you do in SQL Server? MSSQLRecovery is a product that can help you with this and more. Read this review by Dale Elizabeth Corey and see if this product might be something you can use.
2004-12-14
6,779 reads
One of the age old problems in DTS is moving packages between your development, test and production environments. Typically a series of manual edits needs to be done to all the packages to make sure that all the connection objects are pointing to the correct physical servers. This is time consuming and gives rise to the possibility of human error, particularly if the solution incorporates many DTS packages. Many companies have provided their own custom solutions for managing this problem but these are still workarounds for a problem that is inherently DTS's.
2004-12-14
1,761 reads
Deploying a SQL Server database with your software can be tricky. It's easy to forget something that you added to development when trying to script out or detach and copy a database. And there's the whole problem of integrating the installation or upgrade into your main installation routine. New author Mark Vermeulen takes a look at Red Gate's SQLPackager, designed to make the job of deploying a database much easier.
2004-12-13
5,510 reads
The key to effective security is embracing it as an ongoing process rather than a one time event. This document examines how database security can be enhanced with a proactive security lifecycle approach.
2004-12-13
1,564 reads
A short survey from Microsoft looking for feedback from users in order to try and improve the application development process. If you build applications with MS technolgies, especially SQL Server, take a moment and respond.
2004-12-10
2,822 reads
SQL Server has a rock solid backup and restore routine. However, it is not the most efficient way of handling the backups and restores. Neither in terms of time or space required. A number of software vendors have developed their own additions to SQL Server that accelerate or compress the backups (or both). Wesley Brown has taken four of these products into his environment and run some comparisons. Read about large databases in part 2 of this series.
2004-12-09
7,296 reads
SQL Server depends heavily on good indexing to perform well. The optimizer requires relevant and intelligent indexing in order to do its job well. Author Andre Vigneau brings us a script that he uses to detect possible index problems in the database design as well as a number of hints to ensure that your database is performing optimally.
2004-12-08
16,252 reads
SQL Server has a rock solid backup and restore routine. However, it is not the most efficient way of handling the backups and restores. Neither in terms of time or space required. A number of software vendors have developed their own additions to SQL Server that accelerate or compress the backups (or both). New Author Wesley Brown has taken four of these products into his environment and run some comparisons. Read part one of his review.
2004-12-07
10,783 reads
By ChrisJenkins
Have you been thinking about migrating your reporting to Microsoft Fabric or Snowflake but...
By Steve Jones
It’s Prime Day. A few of my recommendations, since I want to do some...
With Fabric Mirroring, Microsoft is promoting a nice and appealing story for operational reporting...
Comments posted to this topic are about the item SQL Art, Part 4: Happy...
Comments posted to this topic are about the item Concurrency and Baseline Control: Level...
Comments posted to this topic are about the item Spending Time in the Office
I have this code on SQL Server 2022. What happens when it runs all at once?
DROP TABLE IF EXISTS dbo.Commission GO CREATE TABLE dbo.Commission (id INT NOT NULL IDENTITY(1,1) CONSTRAINT CommissionPK PRIMARY KEY , salesperson VARCHAR(20) , commission VARCHAR(20) ) GO INSERT dbo.Commission ( salesperson, commission) VALUES ( 'Brian', 12 ), ( 'Brian', 'None' ) GOSee possible answers