DotNetNewsgroup.com  
web access to complete list of Microsoft.NET newsgroups
   home   |   control panel login   |   archive  |  
 
  carried group
academic
adonet
aspnet
aspnet.announcements
aspnet.buildingcontrols
aspnet.caching
aspnet.datagridcontrol
aspnet.mobile
aspnet.security
aspnet.webcontrols
aspnet.webservices
assignment_manager
datatools
dotnet.distributed_apps
dotnet.general
dotnet.myservices
dotnet.nternationalization
dotnet.scripting
dotnet.security
dotnet.vjsharp
dotnet.vsa
dotnet.xml
dotnetfaqs
framework
framework.clr
framework.compactframework
framework.component_services
framework.controls
framework.databinding
framework.drawing
framework.enhancements
framework.interop
framework.odbcnet
framework.performance
framework.remoting
framework.sdk
framework.setup
framework.webservices
framework.windowsforms
framework.wmi
frwk.windowsforms.designtime
lang.csharp
lang.jscript
lang.vb
lang.vb.controls
lang.vb.data
lang.vb.upgrade
lang.vc
lang.vc.libraries
  
 
start date: Mon, 30 Jul 2007 03:45:42 -0700,    posted on: microsoft.public.dotnet.framework.adonet        back       

Thread Index
  1    unknown


Using a .net Custom Data Provider and SQL Server 2005 Management Studio   
Hi,

MS have exposed the functionality to use custom data providers in
Visual Studio 2005, I've used this and it works fine.

I would like to know if it's possible to use a custom data provider
from SSMS? I'm not even sure if SSMS uses a .net data provider under
the covers, - does anyone know?

If it does then does anyone know how SSMS gets a list of databases
from the connected instance?

Background:

We have a specialised solution which manages lots (1000's) of simple
databases (for example a questionaire) for clients built on top of SQL
2005. Each of these databases is a virtual database - they arn't real
databases in SQL 2005. The data for all the databases is stored
vertically in an EAV format in various tables. For convenience I use
my custom data provider to execute SQL against the flattened schema,
and it internally converts the sql using the schema for each "virtual"
database (stored as xml in SQL 2005) to the rather complicated SQL
required to access the real underlying tables.

Best Regards,

Daniel
Date:Mon, 30 Jul 2007 03:45:42 -0700   Author:  

Google
 
Web dotnetnewsgroup.com


COPYRIGHT ?2005, EUROFRONT WORLDWIDE LTD., ALL RIGHT RESERVE  |   Contact us