SQL 2000 User Defined Function Primer
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.
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.
Learn how to use the new notification technologies in ADO.NET 2.0 and SQL Server 2005 to handle ad-hoc data refreshes.
It is Friday, the queries are running, and nobody is watching the bill. That...
By Steve Jones
Annabel retired from Redgate Software this week. Across most of my career at Redgate,...
By Tim Radney
As a SQL Server DBA with years of experience tuning production environments, I’ve seen...
Comments posted to this topic are about the item What is the Cloud?
Comments posted to this topic are about the item Changing the Schema
Comments posted to this topic are about the item Index Fragmentation Explained: Page Splits,...
I set up a few users on my SQL Server 2022 instance.
CREATE LOGIN User1 WITH PASSWORD = 'Demo12#1' CREATE USER User1 FOR LOGIN User1 GO CREATE LOGIN User2 WITH PASSWORD = 'Demo12#2' CREATE USER User2 FOR LOGIN User2 GO CREATE LOGIN User3 WITH PASSWORD = 'Demo12#3' CREATE USER User3 FOR LOGIN User3 GOI then created a schema that one of them owned. Under this schema, I added a table with some data.
CREATE SCHEMA MySchema AUTHORIZATION User1
GO
CREATE TABLE Myschema.MyTable(myid INT)
GO
INSERT MySchema.MyTable
(
myid
)
VALUES
(1), (2), (3)
GO
SELECT * FROM MySchema.MyTable
GO
I granted rights and verified that User2 could access this table.
GRANT SELECT ON Myschema.MyTable TO User2 GO SETUSER 'USER2' GO SELECT * FROM MySchema.MyTable GOThis worked. Now, I move this schema to a new user.
ALTER AUTHORIZATION ON SCHEMA::Myschema TO User3; GOWhat happens with this code?
SETUSER 'USER2' GO SELECT * FROM MySchema.MyTable GOSee possible answers