Technical Article

Enumerate SQL Servers using SQLDMO and T-SQL

Microsoft reported BUG :ListAvailableServers Method of the SQLDMO.Application Object Causes Error 0x800A000E .When you execute the ListAvailableServers method of the SQLDMO.Application object from an ASP page, the following error message may occur: Microsoft SQL-DMO (0x800A000E) [SQL-DMO]Not enough storage is available to complete this operation. However, there is some solution to get SQL servers using Client […]

You rated this post out of 5. Change rating

2002-06-19

466 reads

Blogs

A New Word: the Wends

By

the wends– n. the frustration that you’re not enjoying an experience as much as...

7 Best Online Advanced SQL Training Courses to Learn in 2024 and Beyond

By

The world runs on data, and SQL is the key to unlocking its secrets....

Manually Updating Redgate Monitor/SQL Monitor Patch Info

By

This post looks at updating the patch information for SQL Monitor/Redgate Monitor without using...

Read the latest Blogs

Forums

There's No Free Lunch with Open-source Software

By Ryan Booz

Comments posted to this topic are about the item There's No Free Lunch with...

Upgrading SSRS 2016 to SSRS 2019 in place

By koln

Server A has SSRS 2016 on it and I would now like to upgrade...

Pipeline Failure Route not working

By rjdineen

Hi there, I have a couple of Stored Proc tasks, that fire off after...

Visit the forum

Question of the Day

Default Objects in Clones

On SQL Server 2022, I do this:

USE model
GO
CREATE TABLE dbo.DBALog
(logdate DATETIME2(3), logmsg VARCHAR(2000))
GO
I then create a new database:
CREATE DATABASE INVENTORY
GO
I install a new database application in here with multiple tables, views, etc. I do not run any queries. I then decide to run this code:
DBCC CLONEDATABASE(INVENTORY, Inventory_clone);
GO
What happens?

See possible answers