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,080 reads
SQL Server shows lots of information in Enterprise Manager, but getting a report for someone or manipulating this data is hard from the GUI. Using T-SQL, it's easier, but sometimes not obvious how to get the data. Author Santveer Singh brings us a way to get at some of that information, the users and their database roles.
2004-11-02
23,780 reads
Knowing which databases are being backed up is a critical thing for all DBAs to know. After reading an article on this subject, new author Santveer Singh decided to share his own techniques for checking SQL Server databases and their backup status. He shows us how to look for failed backups as well as find those databases which have not been backed up.
2004-06-09
9,511 reads
By Steve Jones
In a previous post, I deployed a model to a database using SQL Compare...
By SQLPals
Reality (And Limits) of Instant File Initialization for Transaction Logs in SQL Server 2022 ...
By Steve Jones
Last week I spent a few days in Cambridge, UK for the Redgate Company...
Comments posted to this topic are about the item Adding and Dropping Columns II
Comments posted to this topic are about the item Leveraging DuckDB for OLAP Workloads:...
Comments posted to this topic are about the item More Documentation is Needed
I have this table in my SQL Server 2022 database:
CREATE TABLE [dbo].[CityList] ( [CityNameID] [int] NOT NULL IDENTITY(1, 1), [CityName] [varchar] (30) , [Country2] [char] (3), [stateprovince2] [char] (2), [Country] [char] (3), [stateprovince] [char] ) ON [PRIMARY] GOI decide to drop the stateprovince2 and country2 columns. What code should I use? See possible answers
