Migrating Logins To Another Server
Migrating your logins can be done the easy way or the hard way. Greg shows you one way - care to guess which way?!
2003-09-30
20,644 reads
Migrating your logins can be done the easy way or the hard way. Greg shows you one way - care to guess which way?!
2003-09-30
20,644 reads
Greg returns with an article based on some practical experience using QA templates to save time and work. Good examples, good work through, good idea!
2003-04-28
10,330 reads
With SQL Server 2000 you are able to create databases or columns with a different collating setting than the server. This article will explain a couple of methods Greg has used to successfully change collation settings.
2002-12-30
8,744 reads
A few months ago Greg Larsen ran across a big problem with SQL Server collation when querying. He shares his bruises in this quick article.
2002-12-19
12,800 reads
In this article by Greg Larsen, he shows you how to remove those pesky orphaned users that can be a security risk after restoring to a new server.
2002-11-18
16,112 reads
Occassionally you might want to convert a binary number into some printable string. This would allow you display some meaning fully numbers hex characters, instead of just some unreadable garbage. This script takes a binary field, of basically any length, and converts it, character by character, to a character string. The character string will contain […]
2002-11-07
464 reads
Are you tired of manually restoring each database on a new server when the original server has a melt down? Does the manual process seem slow, and prone to keystoke and mouse click errors? Would you like to have those restore scripts automatically built, so you only have to fire them off? Well this article will show you one possible method for speeding up and reducing errors will trying to perform a restore of all databases on a server.
2002-11-05
9,024 reads
Every want to keep everyone from updating all your users database? If so this script will set each database to read only status.
2002-09-26
338 reads
Every want an easy way to set all database to DBO only and single user mode? Well here is a script to do that for you. This script is useful when you want to keep users out of the all the databases.
2002-09-23
1,316 reads
Here is a companion script to "Set All databases to DBO only and Single User Mode" that will turn off dbo and single user mode for all databases.
2002-09-23
514 reads
By Steve Jones
ecstatic shock – n. a surge of energy upon catching a glimpse from someone...
By Chris Yates
The New Arena of Leadership The role of the Chief Data Officer is no...
Presenting you with an updated version of our sp_snapshot procedure, allowing you to easily...
Just saw the "Azure Extension for SQL Server" Does anyone has experience with it?...
I've noticed several instances of what looks like a recursive insert with the format:...
Comments posted to this topic are about the item Cleaning Up the Cloud
I have a table with this data:
TravelLogID CityID StartDate EndDate 1 1 2025-01-01 2025-01-06 2 2 2025-01-01 2025-01-06 3 3 2025-01-01 2025-01-06 4 4 2025-01-01 2025-01-06 5 5 2025-01-01 2025-01-06I run this code:
SELECT IDENT_CURRENT('TravelLog')I get the value 5 back. Now I do this:
SET IDENTITY_INSERT dbo.TravelLog ON INSERT dbo.TravelLog ( TravelLogID, CityID, StartDate, EndDate ) VALUES (25, 5, '2025-09-12', '2025-09-17') SET IDENTITY_INSERT dbo.TravelLog OFFI now run this code.
DBCC CHECKIDENT(TravelLog) GO INSERT dbo.TravelLog ( CityID, StartDate, EndDate ) VALUES (4, '2025-10-14', '2025-10-17') GOWhat is the value for TravelLogID for the row I inserted for CityID 4 and dates starting on 14 Oct 2025? See possible answers