Merging two dbs: run

Showing posts with label run. Show all posts

Friday, March 30, 2012

Microsoft SQL Server Best Practices Analyzer

Should this tool be installed and run in a production server?
MM
barney@.newsgroups.nospam
Martin,
If you are concerned about installing this tool on production server, you
can install this tool on a remote machine and you could analyze a production
server from a remote machine (as long as you can connect to target SQL
Server from remote machine)
SQL Best Practices Analyzer relies on the BPA Repository database, which is
a SQL Server database created during SQL BPA installation. You can have this
BPA repository database created on local SQL Server or a remote SQL Server.
SQL Best Practices Analyzer requires the following components to be
installed on the machine
.. Microsoft Internet Explorer 6.0 or later
.. Microsoft .Net Framework 1.1
Reference:
http://www.microsoft.com/downloads/d...displaylang=en
Thanks
Sethu
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm.
"Martin Millar" <barney@.newsgroups.nospam> wrote in message
news:7C86BCA9-E805-48F2-91DD-E707914E9102@.microsoft.com...
> Should this tool be installed and run in a production server?
> --
> MM
> barney@.newsgroups.nospam
|||Thanks for this. perhaps I should have been a bit more precise. I am a
developer and I'm having a beef with my DBA who has installed this on the
live production server. My argument is that this should be installed and run
on a test system as there is no need to test the performance of the hardware
on which the DB runs on.
If it's OK on Test then it gets ported to live. I believe that anything that
does not need to be installed on a production server should not be on there
as there is a danger that something else running on the box may result in a
loss of service or may intoduce a risk of virus or attack. This tool requires
the dot.net framework and I am a strong fan of this being an asp.net
developer. But until this (dot.net) becomes a core part of the OS (i.e. when
it's installed by default on XP, win2003 etc) I categorise this as a
development add-on and has an attached if installed.
If MS release a security patch for dot.net then I need to schedule downtime
on the production server to apply this.
So back to my original question, which is in itself is about best practises,
should it be best practise to install the BPA on a production server?
Thanks in advance
"Sethu Srinivasan [MSFT]" wrote:

> Martin,
> If you are concerned about installing this tool on production server, you
> can install this tool on a remote machine and you could analyze a production
> server from a remote machine (as long as you can connect to target SQL
> Server from remote machine)
> SQL Best Practices Analyzer relies on the BPA Repository database, which is
> a SQL Server database created during SQL BPA installation. You can have this
> BPA repository database created on local SQL Server or a remote SQL Server.
> SQL Best Practices Analyzer requires the following components to be
> installed on the machine
> .. Microsoft Internet Explorer 6.0 or later
> .. Microsoft .Net Framework 1.1
> Reference:
> http://www.microsoft.com/downloads/d...displaylang=en
>
> Thanks
> Sethu
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm.
>
> "Martin Millar" <barney@.newsgroups.nospam> wrote in message
> news:7C86BCA9-E805-48F2-91DD-E707914E9102@.microsoft.com...
>
>

Wednesday, March 28, 2012

Microsoft SQL Server 2000 JDBC Driver issue

I was wondering if anybody has run into the following problem with ms's
jdbc driver. We're using cursors in our app - when we create a
java.sql.Statement object in the app, we're indicating that we want the
corresponding ResultSet object to have a TYPE_FORWARD_ONLY cursor.
We've noticed when we do this that if the app executes a query with
'UNION's in it, it never gets a ResultSet back from the server (I've
noticed on the SQL server profiler that it stays stuck doing the 'exec
sp_cursoropen' call). If we change the resultSetType to
TYPE_SCROLL_INSENSITIVE then the query returns in no time.
Any ideas?
Thanks.
--Yogesh
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
joe wrote:

> I was wondering if anybody has run into the following problem with ms's
> jdbc driver. We're using cursors in our app - when we create a
> java.sql.Statement object in the app, we're indicating that we want the
> corresponding ResultSet object to have a TYPE_FORWARD_ONLY cursor.
> We've noticed when we do this that if the app executes a query with
> 'UNION's in it, it never gets a ResultSet back from the server (I've
> noticed on the SQL server profiler that it stays stuck doing the 'exec
> sp_cursoropen' call). If we change the resultSetType to
> TYPE_SCROLL_INSENSITIVE then the query returns in no time.
If you can show an example of your code, it'll help.
If you do a trivial query like "select * from sysdatabases UNION select * from sysdatabases"
that hangs?
thanks
Joe

> Any ideas?
> Thanks.
> --Yogesh
> *** Sent via Developersdex http://www.codecomments.com ***
> Don't just participate in USENET...get rewarded for it!
sql

Microsoft SQL Server 2000 Developer Edition

Hi,
Can anyone confirm that the Microsoft SQL Server 2000 Developer Edition
includes a fully functional version of Enterprise Manager.
I want to run a database at work using MSDE (it's a small but complex db).
Also, would the single user license be appropriate for work use (I will be
the only administrator/developer).
Regards,
Ron.Hi
Yes it does.
According to the EULA, developer edition may only be used for development
and not for production use.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Ron" <Ron@.discussions.microsoft.com> wrote in message
news:93C38BBF-48A6-4D08-B85B-701B3319CA36@.microsoft.com...
> Hi,
> Can anyone confirm that the Microsoft SQL Server 2000 Developer Edition
> includes a fully functional version of Enterprise Manager.
> I want to run a database at work using MSDE (it's a small but complex db).
> Also, would the single user license be appropriate for work use (I will be
> the only administrator/developer).
> Regards,
> Ron.|||To add to Mike's response, Developer Edition contains all the features of
the Enterprise Edition, including GUI client tools. The only difference is
licensing.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Ron" <Ron@.discussions.microsoft.com> wrote in message
news:93C38BBF-48A6-4D08-B85B-701B3319CA36@.microsoft.com...
> Hi,
> Can anyone confirm that the Microsoft SQL Server 2000 Developer Edition
> includes a fully functional version of Enterprise Manager.
> I want to run a database at work using MSDE (it's a small but complex db).
> Also, would the single user license be appropriate for work use (I will be
> the only administrator/developer).
> Regards,
> Ron.|||Thanks guys,
I think I'll have to stay with my current limitations then! (my company
won't spend much for smallish projects)
I can probably do what I need using Access 2000 as a front-end to MSDE. I
was hoping to make use of the DTS (and other) features of Enterprise Manager.
Alternatively, does anyone know of a good third-party MSSQL manager?
Regards,
Ron.

Microsoft SQL Server 2000 Developer Edition

Hi,
Can anyone confirm that the Microsoft SQL Server 2000 Developer Edition
includes a fully functional version of Enterprise Manager.
I want to run a database at work using MSDE (it's a small but complex db).
Also, would the single user license be appropriate for work use (I will be
the only administrator/developer).
Regards,
Ron.Hi
Yes it does.
According to the EULA, developer edition may only be used for development
and not for production use.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Ron" <Ron@.discussions.microsoft.com> wrote in message
news:93C38BBF-48A6-4D08-B85B-701B3319CA36@.microsoft.com...
> Hi,
> Can anyone confirm that the Microsoft SQL Server 2000 Developer Edition
> includes a fully functional version of Enterprise Manager.
> I want to run a database at work using MSDE (it's a small but complex db).
> Also, would the single user license be appropriate for work use (I will be
> the only administrator/developer).
> Regards,
> Ron.|||To add to Mike's response, Developer Edition contains all the features of
the Enterprise Edition, including GUI client tools. The only difference is
licensing.
Hope this helps.
Dan Guzman
SQL Server MVP
"Ron" <Ron@.discussions.microsoft.com> wrote in message
news:93C38BBF-48A6-4D08-B85B-701B3319CA36@.microsoft.com...
> Hi,
> Can anyone confirm that the Microsoft SQL Server 2000 Developer Edition
> includes a fully functional version of Enterprise Manager.
> I want to run a database at work using MSDE (it's a small but complex db).
> Also, would the single user license be appropriate for work use (I will be
> the only administrator/developer).
> Regards,
> Ron.|||Thanks guys,
I think I'll have to stay with my current limitations then! (my company
won't spend much for smallish projects)
I can probably do what I need using Access 2000 as a front-end to MSDE. I
was hoping to make use of the DTS (and other) features of Enterprise Manager
.
Alternatively, does anyone know of a good third-party MSSQL manager?
Regards,
Ron.

Microsoft SQL Server 2000 Developer Edition

Hi,
Can anyone confirm that the Microsoft SQL Server 2000 Developer Edition
includes a fully functional version of Enterprise Manager.
I want to run a database at work using MSDE (it's a small but complex db).
Also, would the single user license be appropriate for work use (I will be
the only administrator/developer).
Regards,
Ron.
Hi
Yes it does.
According to the EULA, developer edition may only be used for development
and not for production use.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Ron" <Ron@.discussions.microsoft.com> wrote in message
news:93C38BBF-48A6-4D08-B85B-701B3319CA36@.microsoft.com...
> Hi,
> Can anyone confirm that the Microsoft SQL Server 2000 Developer Edition
> includes a fully functional version of Enterprise Manager.
> I want to run a database at work using MSDE (it's a small but complex db).
> Also, would the single user license be appropriate for work use (I will be
> the only administrator/developer).
> Regards,
> Ron.
|||To add to Mike's response, Developer Edition contains all the features of
the Enterprise Edition, including GUI client tools. The only difference is
licensing.
Hope this helps.
Dan Guzman
SQL Server MVP
"Ron" <Ron@.discussions.microsoft.com> wrote in message
news:93C38BBF-48A6-4D08-B85B-701B3319CA36@.microsoft.com...
> Hi,
> Can anyone confirm that the Microsoft SQL Server 2000 Developer Edition
> includes a fully functional version of Enterprise Manager.
> I want to run a database at work using MSDE (it's a small but complex db).
> Also, would the single user license be appropriate for work use (I will be
> the only administrator/developer).
> Regards,
> Ron.
|||Thanks guys,
I think I'll have to stay with my current limitations then! (my company
won't spend much for smallish projects)
I can probably do what I need using Access 2000 as a front-end to MSDE. I
was hoping to make use of the DTS (and other) features of Enterprise Manager.
Alternatively, does anyone know of a good third-party MSSQL manager?
Regards,
Ron.

Microsoft SQL server 2000

I connect to SQL2000 database by Visual Basic. It run well on OS 98 and 2000 but it can't run on window XP with the same configure(MDAC, Visual Basic, Service Pack Version).
The error occurs when the default database(Initial Catalog) changed as the following code:

SqlCnn as new adodb.connection
SqlCnn.open "Connection String" ' Default database is "Product"
SqlCnn.Default Database = "Customer" ' Error occurs at this line of code.

Do you have any ideas to solve this problem?
thank you very much in advance.obvious questions, but are you running .net or 6? and also, are you sure the DSN is set up properly?|||Hi!
thank you very much.
I'm running Visual Basic 6.0 (Not VB.net) and DSN is correct because my program runs well on OS 98 and 2000.
I hope you'll give me countermeasure.

Monday, March 26, 2012

Microsoft Project front end to SQL Server

G'day, I hope someone can help with this.
I have up-sized several of my currently-running MSAcces databases to run on
SQL Server 2000. In each case, the up-sizing wizard worked, with several
understandable errors.
In the code, I have often used CurrentDb to locate other text files
associated with the database. I get a run-time error wherever CurrentDb is
used.
In the help I am told to set a reference, I think, to the SQL Server type
library, or to DAO 3.6. Following the intructions, I have located a reference
to the DAO 3.6 type library, and it is checked.
I have also tried the other suggested solution of creating a reference
object, but I cannot figure out how to do this, either.
Please help if you can.
Regards, Terry
CurrentDB in DAO refers to the Jet engne, which is no longer present
in an Access project. You will need to rewrite significant portions of
your application to work with SQL Server, depending on what you need
to do. A straight port of an Access/Jet application never works
without significant alteration (unless it's extremely simple). If you
are working with text files and other local resources (not on the
server), I'd recommend using an mdb with linked tables rather than an
ADP. That gives you the flexibility of still being able to use DAO
against the Jet engine.
-- Mary
Microsoft Access Developer's Guide to SQL Server
http://www.amazon.com/exec/obidos/ASIN/0672319446
On Tue, 7 Sep 2004 06:29:04 -0700, "mccer"
<mccer@.discussions.microsoft.com> wrote:

>G'day, I hope someone can help with this.
>I have up-sized several of my currently-running MSAcces databases to run on
>SQL Server 2000. In each case, the up-sizing wizard worked, with several
>understandable errors.
>In the code, I have often used CurrentDb to locate other text files
>associated with the database. I get a run-time error wherever CurrentDb is
>used.
>In the help I am told to set a reference, I think, to the SQL Server type
>library, or to DAO 3.6. Following the intructions, I have located a reference
>to the DAO 3.6 type library, and it is checked.
>I have also tried the other suggested solution of creating a reference
>object, but I cannot figure out how to do this, either.
>Please help if you can.
>Regards, Terry
sql

Microsoft Please help-Web Service Problem

We had an app that called across to the web services to run batches of statements. Everything worked fine and now they stopped working. The report can still be ran from report manager. What things do we need to check to find the problem? Any help would be greatly appreciated.

Try turning on tracing and view the logs. Also see event viewer if there are any issues. It could be an issue with the app or connectivity instead of Reporting Services, since the web service is used to service Report Manager.

More info on logging.

http://msdn2.microsoft.com/en-us/library/ms156500.aspx

cheers,

Andrew

|||Thank you Andrew for your prompt response. We will look at the logs and see if that leads us in the right direction.|||

Some security patches were applied to the server in December. Is it possible that these could have messed with the way that authentication is handled?

Patches:

KB925398

KB925454

KB923689

KB911897

KB926247

KB923694

|||The app is getting the message back "The report server cannot open a connection to the report server database. A conection to the database is required for all requests and processing. SQL server does not exist or acess denied."|||Is it possible that any of these security patches could have messed with our authentication? Any suggestions Please.

Microsoft OLE DB Provider for SQL Server error '80040e37'

I get Microsoft OLE DB Provider for SQL Server error '80040e37'

Invalid object name '#t_testTemp484883646'.
when I run the following ASP code:

Code is below

<!#Include File="../includes/adovbs.inc" -->

<%
'-- Setup database connection
Set DataCmd = Server.CreateObject("ADODB.Connection")
Set rsData = Server.CreateObject("ADODB.RecordSet")
Dim varTempTableName
DataCmd.Open Application("DB")
'-- Use a Temp Table so that it gets destroyed automatically in case the page times out
'-- Use a Global Temp Table so that it is available across scopes when I open the record set below
'-- Append a semi unique number to the end because its global it could conflict with another browser running the same report
'varTempTableName = "##t_TestTemp" & Minute(Now()) & Second(Now())
varTempTableName = "#t_TestTemp" & Session.SessionID

strSQL = "Create Table " & varTempTableName & "(TestColumn2 int)"
DataCmd.Execute strSQL

strSQL = "select * from t_Test"
rsData.Open strSQL, DataCmd, adOpenForwardOnly,adLockReadOnly

Do While Not rsData.EOF
varTestColumn2 = rsData("TestColumn2")

'Error occurs when I place the following insert statement. Code works with the global variable

strSQL = "Insert into " & varTempTableName & " (TestColumn2) values (" & varTestColumn2 & ")"
DataCmd.Execute strSQL

rsData.MoveNext
Loop
rsData.Close

strSQL = "Drop Table " & varTempTableName
DataCmd.Execute strSQL

Set rsData = Nothing
Set DataCmd = Nothing
%>
</BODY>
</HTML>

If you have connection pooling enabled you will get *one* of the connection which *could* be actually not the same connection as this which created the temp table. So either use global temp tables (## instead of #) or disable connection pooling.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

Monday, March 19, 2012

Microsoft ASP Licensing Program for SQL Server

I own and run a small ASP that provides membership management services to
non-profit organizations. Currently I host my application on a dedicated
Windows Server 2003 machine at a hosting provider. The application is
..NET-based and makes use of SQL Server databases on a shared SQL Server
machine at said hosting provider.
I have recently been encountering limitations with this usage of SQL
databases on a shared machine. I am ready to purchase my own SQL Server
license. It looks like a per-processor license is the way to go. Because I am
a small operation, I cannot afford outright purchase of SQL Server Enterprise
Edition ($19,000-plus for 1 processor) or SQL Server 2000 Standard Edition
($4,700-plus for 1 processor).
It looks like the program for me may be the Microsoft ASP Licensing Program,
which appears to offer a monthly bill for a SQL Server per-processor license.
But I'm not getting good answers on this program from the published
materials. In particular, my questions are:
1) Is my company eligible for this program? We are a Registered Member in
the Empower Program for ISVs. (Microsoft's "ASP Strategy Whitepaper" says a
company must be a Microsoft Certified Solution Provider to buy from the ASP
Licensing Program. Is this a hoop I need to jump through to buy SQL Server on
the ASP plan?)
2) What is the pricing for this program?
Any help you can offer on these questions would be appreciated.
rxsullivan wrote:
> I own and run a small ASP that provides membership management
You should contact Microsoft directly for this question.
David Gugick
Imceda Software
www.imceda.com
|||I agree that you should contact your local MS office for this. In
Australiia, this particular area is looked after by a "Regional Hosting
Specialist", but he's mainly interested in the SPLA licensing you're
referring to. Make sure you look up what's available to you through your ISV
contacts as my experience is that in some cases, these guys can sometimes
save you more money than through SPLA, especially if you're a leading
product in your field.
What country are you in? I'd be happy to ping my local contact to see if I
can help get you connected.
Regards,
Greg Linwood
SQL Server MVP
"rxsullivan" <rxsullivan@.discussions.microsoft.com> wrote in message
news:A6B1CA2D-E162-477E-A1E9-B2E9EBBEE40A@.microsoft.com...
>I own and run a small ASP that provides membership management services to
> non-profit organizations. Currently I host my application on a dedicated
> Windows Server 2003 machine at a hosting provider. The application is
> .NET-based and makes use of SQL Server databases on a shared SQL Server
> machine at said hosting provider.
> I have recently been encountering limitations with this usage of SQL
> databases on a shared machine. I am ready to purchase my own SQL Server
> license. It looks like a per-processor license is the way to go. Because I
> am
> a small operation, I cannot afford outright purchase of SQL Server
> Enterprise
> Edition ($19,000-plus for 1 processor) or SQL Server 2000 Standard Edition
> ($4,700-plus for 1 processor).
> It looks like the program for me may be the Microsoft ASP Licensing
> Program,
> which appears to offer a monthly bill for a SQL Server per-processor
> license.
> But I'm not getting good answers on this program from the published
> materials. In particular, my questions are:
> 1) Is my company eligible for this program? We are a Registered Member in
> the Empower Program for ISVs. (Microsoft's "ASP Strategy Whitepaper" says
> a
> company must be a Microsoft Certified Solution Provider to buy from the
> ASP
> Licensing Program. Is this a hoop I need to jump through to buy SQL Server
> on
> the ASP plan?)
> 2) What is the pricing for this program?
> Any help you can offer on these questions would be appreciated.

Microsoft ASP Licensing Program for SQL Server

I own and run a small ASP that provides membership management services to
non-profit organizations. Currently I host my application on a dedicated
Windows Server 2003 machine at a hosting provider. The application is
.NET-based and makes use of SQL Server databases on a shared SQL Server
machine at said hosting provider.
I have recently been encountering limitations with this usage of SQL
databases on a shared machine. I am ready to purchase my own SQL Server
license. It looks like a per-processor license is the way to go. Because I am
a small operation, I cannot afford outright purchase of SQL Server Enterprise
Edition ($19,000-plus for 1 processor) or SQL Server 2000 Standard Edition
($4,700-plus for 1 processor).
It looks like the program for me may be the Microsoft ASP Licensing Program,
which appears to offer a monthly bill for a SQL Server per-processor license.
But I'm not getting good answers on this program from the published
materials. In particular, my questions are:
1) Is my company eligible for this program? We are a Registered Member in
the Empower Program for ISVs. (Microsoft's "ASP Strategy Whitepaper" says a
company must be a Microsoft Certified Solution Provider to buy from the ASP
Licensing Program. Is this a hoop I need to jump through to buy SQL Server on
the ASP plan?)
2) What is the pricing for this program?
Any help you can offer on these questions would be appreciated.rxsullivan wrote:
> I own and run a small ASP that provides membership management
You should contact Microsoft directly for this question.
--
David Gugick
Imceda Software
www.imceda.com|||I agree that you should contact your local MS office for this. In
Australiia, this particular area is looked after by a "Regional Hosting
Specialist", but he's mainly interested in the SPLA licensing you're
referring to. Make sure you look up what's available to you through your ISV
contacts as my experience is that in some cases, these guys can sometimes
save you more money than through SPLA, especially if you're a leading
product in your field.
What country are you in? I'd be happy to ping my local contact to see if I
can help get you connected.
Regards,
Greg Linwood
SQL Server MVP
"rxsullivan" <rxsullivan@.discussions.microsoft.com> wrote in message
news:A6B1CA2D-E162-477E-A1E9-B2E9EBBEE40A@.microsoft.com...
>I own and run a small ASP that provides membership management services to
> non-profit organizations. Currently I host my application on a dedicated
> Windows Server 2003 machine at a hosting provider. The application is
> .NET-based and makes use of SQL Server databases on a shared SQL Server
> machine at said hosting provider.
> I have recently been encountering limitations with this usage of SQL
> databases on a shared machine. I am ready to purchase my own SQL Server
> license. It looks like a per-processor license is the way to go. Because I
> am
> a small operation, I cannot afford outright purchase of SQL Server
> Enterprise
> Edition ($19,000-plus for 1 processor) or SQL Server 2000 Standard Edition
> ($4,700-plus for 1 processor).
> It looks like the program for me may be the Microsoft ASP Licensing
> Program,
> which appears to offer a monthly bill for a SQL Server per-processor
> license.
> But I'm not getting good answers on this program from the published
> materials. In particular, my questions are:
> 1) Is my company eligible for this program? We are a Registered Member in
> the Empower Program for ISVs. (Microsoft's "ASP Strategy Whitepaper" says
> a
> company must be a Microsoft Certified Solution Provider to buy from the
> ASP
> Licensing Program. Is this a hoop I need to jump through to buy SQL Server
> on
> the ASP plan?)
> 2) What is the pricing for this program?
> Any help you can offer on these questions would be appreciated.

Microsoft ASP Licensing Program for SQL Server

I own and run a small ASP that provides membership management services to
non-profit organizations. Currently I host my application on a dedicated
Windows Server 2003 machine at a hosting provider. The application is
.NET-based and makes use of SQL Server databases on a shared SQL Server
machine at said hosting provider.
I have recently been encountering limitations with this usage of SQL
databases on a shared machine. I am ready to purchase my own SQL Server
license. It looks like a per-processor license is the way to go. Because I a
m
a small operation, I cannot afford outright purchase of SQL Server Enterpris
e
Edition ($19,000-plus for 1 processor) or SQL Server 2000 Standard Edition
($4,700-plus for 1 processor).
It looks like the program for me may be the Microsoft ASP Licensing Program,
which appears to offer a monthly bill for a SQL Server per-processor license
.
But I'm not getting good answers on this program from the published
materials. In particular, my questions are:
1) Is my company eligible for this program? We are a Registered Member in
the Empower Program for ISVs. (Microsoft's "ASP Strategy Whitepaper" says a
company must be a Microsoft Certified Solution Provider to buy from the ASP
Licensing Program. Is this a hoop I need to jump through to buy SQL Server o
n
the ASP plan?)
2) What is the pricing for this program?
Any help you can offer on these questions would be appreciated.rxsullivan wrote:
> I own and run a small ASP that provides membership management
You should contact Microsoft directly for this question.
David Gugick
Imceda Software
www.imceda.com|||I agree that you should contact your local MS office for this. In
Australiia, this particular area is looked after by a "Regional Hosting
Specialist", but he's mainly interested in the SPLA licensing you're
referring to. Make sure you look up what's available to you through your ISV
contacts as my experience is that in some cases, these guys can sometimes
save you more money than through SPLA, especially if you're a leading
product in your field.
What country are you in? I'd be happy to ping my local contact to see if I
can help get you connected.
Regards,
Greg Linwood
SQL Server MVP
"rxsullivan" <rxsullivan@.discussions.microsoft.com> wrote in message
news:A6B1CA2D-E162-477E-A1E9-B2E9EBBEE40A@.microsoft.com...
>I own and run a small ASP that provides membership management services to
> non-profit organizations. Currently I host my application on a dedicated
> Windows Server 2003 machine at a hosting provider. The application is
> .NET-based and makes use of SQL Server databases on a shared SQL Server
> machine at said hosting provider.
> I have recently been encountering limitations with this usage of SQL
> databases on a shared machine. I am ready to purchase my own SQL Server
> license. It looks like a per-processor license is the way to go. Because I
> am
> a small operation, I cannot afford outright purchase of SQL Server
> Enterprise
> Edition ($19,000-plus for 1 processor) or SQL Server 2000 Standard Edition
> ($4,700-plus for 1 processor).
> It looks like the program for me may be the Microsoft ASP Licensing
> Program,
> which appears to offer a monthly bill for a SQL Server per-processor
> license.
> But I'm not getting good answers on this program from the published
> materials. In particular, my questions are:
> 1) Is my company eligible for this program? We are a Registered Member in
> the Empower Program for ISVs. (Microsoft's "ASP Strategy Whitepaper" says
> a
> company must be a Microsoft Certified Solution Provider to buy from the
> ASP
> Licensing Program. Is this a hoop I need to jump through to buy SQL Server
> on
> the ASP plan?)
> 2) What is the pricing for this program?
> Any help you can offer on these questions would be appreciated.

Wednesday, March 7, 2012

Messed up SQL 2000 - Error Code 193

Somehow my SQL Server 2000 installation got messed up and refuses to run. I
narrowed it down, I believe, to a problem of the DLL drivers for SQL Server
being out of sync with the location the Registry had for them.
When I now attempt to create a SQL Server ODBC connection, I get:
"The setup routines for the ODBC Driver could not be loaded due to System
Error Code 193." I then get a message about the translator files failing.
I tried installing the latest MDAC, but it says my operating system already
has MDAC and won't install them.
Anyone ever see this...and have any ideas on fixing this and getting my SQL
Server running again?
Much thanks,
B. Rosman
Chicago, IL
Rosman Computing said (on or about) 12/10/2006 03:28:
> Somehow my SQL Server 2000 installation got messed up and refuses to run. I
> narrowed it down, I believe, to a problem of the DLL drivers for SQL Server
> being out of sync with the location the Registry had for them.
> When I now attempt to create a SQL Server ODBC connection, I get:
> "The setup routines for the ODBC Driver could not be loaded due to System
> Error Code 193." I then get a message about the translator files failing.
> I tried installing the latest MDAC, but it says my operating system already
> has MDAC and won't install them.
> Anyone ever see this...and have any ideas on fixing this and getting my SQL
> Server running again?
> Much thanks,
> B. Rosman
> Chicago, IL
I ran into a similar problem with the ODBC Setup. In my case the SQL
Server was not affected because it was running on a server and the
ODBC Setup problem occurred on the client.
As I recall, the situation came about because the client PC had a
newer version of MDAC on it than the one on the SQL Server
installation disc. When I used the SQL Server installation disc to
install the SQL Server tools on the client, the ODBC Setup programs
went out of sync and when I tried to either create a new ODBC
connection (or modify an existing one) I got an error about not being
able to load the setup routines.
I was never able to resolve the problem. Since I only had one
application that needed to access SQL Server and it already had a
valid connection, it wasn't a big problem. When I needed to make a
second connection to a different db (test instance), I just looked at
the various registry settings for the existing one and duplicated them
for the 2nd. I no longer have the problem because that client PC was
recycled and I made sure that the SQL Server tools were installed on
the new one before I did anything like upgrading MDAC.
|||I was able to fix it anyway. I installed the SQL Server 2000 Server Pack, and
that automatically installed the SQLSRV32.DLL into the system directory. It
worked after doing that.
Thanks,
Bill r.
"DGA" wrote:

> Rosman Computing said (on or about) 12/10/2006 03:28:
> I ran into a similar problem with the ODBC Setup. In my case the SQL
> Server was not affected because it was running on a server and the
> ODBC Setup problem occurred on the client.
> As I recall, the situation came about because the client PC had a
> newer version of MDAC on it than the one on the SQL Server
> installation disc. When I used the SQL Server installation disc to
> install the SQL Server tools on the client, the ODBC Setup programs
> went out of sync and when I tried to either create a new ODBC
> connection (or modify an existing one) I got an error about not being
> able to load the setup routines.
> I was never able to resolve the problem. Since I only had one
> application that needed to access SQL Server and it already had a
> valid connection, it wasn't a big problem. When I needed to make a
> second connection to a different db (test instance), I just looked at
> the various registry settings for the existing one and duplicated them
> for the 2nd. I no longer have the problem because that client PC was
> recycled and I made sure that the SQL Server tools were installed on
> the new one before I did anything like upgrading MDAC.
>

Saturday, February 25, 2012

Messed up SQL 2000 - Error Code 193

Somehow my SQL Server 2000 installation got messed up and refuses to run. I
narrowed it down, I believe, to a problem of the DLL drivers for SQL Server
being out of sync with the location the Registry had for them.
When I now attempt to create a SQL Server ODBC connection, I get:
"The setup routines for the ODBC Driver could not be loaded due to System
Error Code 193." I then get a message about the translator files failing.
I tried installing the latest MDAC, but it says my operating system already
has MDAC and won't install them.
Anyone ever see this...and have any ideas on fixing this and getting my SQL
Server running again?
Much thanks,
B. Rosman
Chicago, ILRosman Computing said (on or about) 12/10/2006 03:28:
> Somehow my SQL Server 2000 installation got messed up and refuses to run.
I
> narrowed it down, I believe, to a problem of the DLL drivers for SQL Serve
r
> being out of sync with the location the Registry had for them.
> When I now attempt to create a SQL Server ODBC connection, I get:
> "The setup routines for the ODBC Driver could not be loaded due to System
> Error Code 193." I then get a message about the translator files failing.
> I tried installing the latest MDAC, but it says my operating system alread
y
> has MDAC and won't install them.
> Anyone ever see this...and have any ideas on fixing this and getting my SQ
L
> Server running again?
> Much thanks,
> B. Rosman
> Chicago, IL
I ran into a similar problem with the ODBC Setup. In my case the SQL
Server was not affected because it was running on a server and the
ODBC Setup problem occurred on the client.
As I recall, the situation came about because the client PC had a
newer version of MDAC on it than the one on the SQL Server
installation disc. When I used the SQL Server installation disc to
install the SQL Server tools on the client, the ODBC Setup programs
went out of sync and when I tried to either create a new ODBC
connection (or modify an existing one) I got an error about not being
able to load the setup routines.
I was never able to resolve the problem. Since I only had one
application that needed to access SQL Server and it already had a
valid connection, it wasn't a big problem. When I needed to make a
second connection to a different db (test instance), I just looked at
the various registry settings for the existing one and duplicated them
for the 2nd. I no longer have the problem because that client PC was
recycled and I made sure that the SQL Server tools were installed on
the new one before I did anything like upgrading MDAC.|||I was able to fix it anyway. I installed the SQL Server 2000 Server Pack, an
d
that automatically installed the SQLSRV32.DLL into the system directory. It
worked after doing that.
Thanks,
Bill r.
"DGA" wrote:

> Rosman Computing said (on or about) 12/10/2006 03:28:
> I ran into a similar problem with the ODBC Setup. In my case the SQL
> Server was not affected because it was running on a server and the
> ODBC Setup problem occurred on the client.
> As I recall, the situation came about because the client PC had a
> newer version of MDAC on it than the one on the SQL Server
> installation disc. When I used the SQL Server installation disc to
> install the SQL Server tools on the client, the ODBC Setup programs
> went out of sync and when I tried to either create a new ODBC
> connection (or modify an existing one) I got an error about not being
> able to load the setup routines.
> I was never able to resolve the problem. Since I only had one
> application that needed to access SQL Server and it already had a
> valid connection, it wasn't a big problem. When I needed to make a
> second connection to a different db (test instance), I just looked at
> the various registry settings for the existing one and duplicated them
> for the 2nd. I no longer have the problem because that client PC was
> recycled and I made sure that the SQL Server tools were installed on
> the new one before I did anything like upgrading MDAC.
>

Monday, February 20, 2012

Message OFF

In the query analyzer when I run the command
create database TestingDb
I can see the messages
The CREATE DATABASE process is allocating 0.63 MB on disk 'TestingDb'.
The CREATE DATABASE process is allocating 0.49 MB on disk 'TestingDb_log'.
I want to hide the message, how can I do that?
Thanks
We can not turn off those messages in query analyzer or management studio.
Thanks
Hari
"Rogers" <naissani@.hotmail.com> wrote in message
news:OyZC18InHHA.4424@.TK2MSFTNGP03.phx.gbl...
> In the query analyzer when I run the command
> create database TestingDb
> I can see the messages
> The CREATE DATABASE process is allocating 0.63 MB on disk 'TestingDb'.
> The CREATE DATABASE process is allocating 0.49 MB on disk 'TestingDb_log'.
> I want to hide the message, how can I do that?
> Thanks
>

Message compression

We have run some tests on our application. Average message is about 2.5 MB. Messages are send once every 30 minutes. This is 3.5 Gb per month for one site. Now we already have three sites that will be sending this messages. This will be VERY high load on the WAN channel, and will cost us a LOT of money Tongue Tied

.
Isn't it possible to add some compression? XML should compress very well, this feature will make brokers more useful.Service Broker messages are not required to be XML. They can simply be blobs. So you could perform the compression and decompression fairly easily in your app and send compressed messages through the Broker. That way you control the compression algorithms and not the system.|||

Some tips for reducing the traffic when using Service Broker:
- use binary messages instead of XML
- compress the message payload in the application, before calling SEND
- use one long lived dialog to send all messages, don't start a new dialog for every message
- few large messages is better than many small messages
- use short names for services, contracts, message types

I'd add that Service Broker is quite unchaty. For instance, there is no handshake for dialogs: first message SEND on the dialog is the first message sent on the wire.

HTH,
~ Remus

Message --"Configuration option 'show advanced options' changed from 0 to 1. Run the RECO

i am working on storedprocedures and after the Succesful parsing of the procedure .. on executing its giving me 3 msgs ....

Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install.

Configuration option 'xp_cmdshell' changed from 1 to 1. Run the RECONFIGURE statement to install.

Configuration option 'show advanced options' changed from 1 to 0. Run the RECONFIGURE statement to install.

and not displaying me the output.......

The Procedure i am executing is as follows

set ANSI_NULLS ON

set QUOTED_IDENTIFIER ON

CREATE PROCEDURE [dbo].[uspRcopiaExport12] AS

DROP TABLE Skagway..RCOPIA_EXPORT

-- Get Patients' Home Addresses

SELECT pa.PersonID, pa.Street1, pa.Street2, pa.City, pa.State, Skagway.dbo.StripNonDigits(pa.ZipCode) AS Zip

INTO #ADDRESS

FROM Person..PHYSICAL_ADDRESS pa

INNER JOIN Person..PHYSICAL_ADDRESS_DESC pad ON (pa.PhysicalAddrDescID = pad.PhysicalAddrDescID)

WHERE pad.PhysicalAddrDesc = 'Home'

-- Get Patients' Home Phone Numbers

SELECT tn.PersonID, tn.TelecomNumber

INTO #HOME_PHONE

FROM Person..TELECOM_NUMBER tn

INNER JOIN Person..TELECOM_NUMBER_DESC tnd ON (tn.TelecomNumDescID = tnd.TelecomNumDescID)

INNER JOIN Person..TELECOM_DEVICE_TYPE tdt ON (tn.TelecomDevTypeID = tdt.TelecomDevTypeID)

WHERE tnd.TelecomNumDesc = 'Home'

ORDER BY tdt.TelecomDevTypeID

-- Get Patients' Work Phone Numbers

SELECT tn.PersonID, tn.TelecomNumber

INTO #WORK_PHONE

FROM Person..TELECOM_NUMBER tn

INNER JOIN Person..TELECOM_NUMBER_DESC tnd ON (tn.TelecomNumDescID = tnd.TelecomNumDescID)

INNER JOIN Person..TELECOM_DEVICE_TYPE tdt ON (tn.TelecomDevTypeID = tdt.TelecomDevTypeID)

WHERE tnd.TelecomNumDesc = 'Work'

ORDER BY tdt.TelecomDevTypeID

-- Get SCP patient demographic data

SELECT 'update_patient_4' AS DataType,

p.FirstName AS FIRST_NAME,

p.MiddleInit AS MIDDLE_INITIAL,

p.LastName AS LAST_NAME,

CASE p.Gender

WHEN 'm' THEN 'M'

WHEN 'f' THEN 'F'

WHEN 'M' THEN 'M'

WHEN 'F' THEN 'F'

ELSE 'U'

END AS SEX,

-- (SELECT TOP 1 Street1 FROM #ADDRESS WHERE PersonID = p.PersonID) AS ADDRESS_LINE_1,

-- (SELECT TOP 1 Street2 FROM #ADDRESS WHERE PersonID = p.PersonID) AS ADDRESS_LINE_2,

-- (SELECT TOP 1 City FROM #ADDRESS WHERE PersonID = p.PersonID) AS CITY,

-- (SELECT TOP 1 State FROM #ADDRESS WHERE PersonID = p.PersonID) AS STATE_CODE,

-- (SELECT TOP 1 Zip FROM #ADDRESS WHERE PersonID = p.PersonID) AS ZIP,

-- (SELECT TOP 1 TelecomNumber FROM #HOME_PHONE WHERE PersonID = p.PersonID) AS PHONE,

-- (SELECT TOP 1 TelecomNumber FROM #WORK_PHONE WHERE PersonID = p.PersonID) AS WORK_PHONE,

' 'AS ADDRESS_LINE_1,

' 'AS ADDRESS_LINE_2,

' 'AS CITY,

' 'AS STATE_CODE,

' 'AS ZIP,

' 'AS PHONE,

' 'AS WORK_PHONE,

' ' AS OTHER_PHONE,

-- ea.EmailAddress AS EMAIL,

' ' AS EMAIL,

p.BirthDate AS BIRTHDATE,

p.SocSecNum AS SOCIAL_SECURITY,

' ' AS INSURANCE,

' ' AS LAST_VISIT_DATE,

'PHMS-SCP-' + CAST(p.PersonID AS VARCHAR(8)) AS EXTERNAL_ID,

' ' AS PROVIDER_FIRST_NAME,

' ' AS PROVIDER_MIDDLE_NAME,

' ' AS PROVIDER_LAST_NAME

INTO Skagway..RCOPIA_EXPORT

FROM Skagway..PERSON p

INNER JOIN Skagway..EMAIL_ADDRESS ea ON (p.PersonID=ea.PersonID)

INNER JOIN Skagway..CARE_TEAM_ASSIGNMENT cta ON (p.PersonID=cta.PersonID)

INNER JOIN Skagway..SHARED_CARE_PLAN scp ON (cta.CarePlanID=scp.CarePlanID)

WHERE scp.SCPInactiveFlag <> 1

AND cta.CareTeamRoleID = 23

AND p.BirthDate IS NOT NULL

AND p.SocSecNum IS NOT NULL

AND NOT p.SocSecNum IN ('999999999', '')

-- Replace all NULLs with single spaces (required by Rcopia for import)

UPDATE Skagway..RCOPIA_EXPORT

SET MIDDLE_INITIAL = ' '

WHERE MIDDLE_INITIAL IS NULL OR MIDDLE_INITIAL = ''