Showing posts with label msde. Show all posts
Showing posts with label msde. Show all posts

Thursday, March 29, 2012

About a Free MSDE manager

Hello!!
Can you advice me some free MSDE tools (like database manager, query
interface...) that can be found over web?
Thanks in advance for your help!!
Ambros Moreno
From Almeria (Spain)
http://www.aspfaq.com/2442
http://www.aspfaq.com/
(Reverse address to reply.)
"Ambros" <ambros@.sasao.com> wrote in message
news:Obexjnf1EHA.2804@.TK2MSFTNGP15.phx.gbl...
> Hello!!
> Can you advice me some free MSDE tools (like database manager, query
> interface...) that can be found over web?
> Thanks in advance for your help!!
> Ambros Moreno
> From Almeria (Spain)
>
|||Thanks for the link Aaron!! is really usefull.!!
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> escribi en el mensaje
news:eOwVYai1EHA.2156@.TK2MSFTNGP10.phx.gbl...
> http://www.aspfaq.com/2442
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
>
> "Ambros" <ambros@.sasao.com> wrote in message
> news:Obexjnf1EHA.2804@.TK2MSFTNGP15.phx.gbl...
>

Tuesday, March 27, 2012

Aborting CALL to stored procedure

Hello

I am calling a stored procedure in a MSDE/SQLServer DB form within my
Visual C++ 6.0 program along the lines
CCommand<CAccessor<CdboMyAccessor>>::Open(m_session, NULL);
With
DEFINE_COMMAND(CdboMyAccessor, _T("{ CALL dbo.MyProc; 1(?,?) }"))
It all works sweet as, but it can take a while and I want to let the
user abort it.
Everything I've tried ends in tears.Hi

You can issue a KILL command on the SQL Server which will terminate the
process. To do this you are going to need a separate thread. More
information in books online.

John

"Mike Brown" <browna@.beer.com> wrote in message
news:ea197978.0406302059.3f4b8524@.posting.google.c om...
> Hello
> I am calling a stored procedure in a MSDE/SQLServer DB form within my
> Visual C++ 6.0 program along the lines
> CCommand<CAccessor<CdboMyAccessor>>::Open(m_session, NULL);
> With
> DEFINE_COMMAND(CdboMyAccessor, _T("{ CALL dbo.MyProc; 1(?,?) }"))
> It all works sweet as, but it can take a while and I want to let the
> user abort it.
> Everything I've tried ends in tears.|||I have the command running in a separate thread.
I dont want to kill the server, just the CALL. I have tried killing
the thread and using .Abort(), and most other things I can think of,
but everything results in my program crashing.

"John Bell" <jbellnewsposts@.hotmail.com> wrote in message news:<AKPEc.694$t8.6278387@.news-text.cableinet.net>...
> Hi
> You can issue a KILL command on the SQL Server which will terminate the
> process. To do this you are going to need a separate thread. More
> information in books online.
> John
> "Mike Brown" <browna@.beer.com> wrote in message
> news:ea197978.0406302059.3f4b8524@.posting.google.c om...
> > Hello
> > I am calling a stored procedure in a MSDE/SQLServer DB form within my
> > Visual C++ 6.0 program along the lines
> > CCommand<CAccessor<CdboMyAccessor>>::Open(m_session, NULL);
> > With
> > DEFINE_COMMAND(CdboMyAccessor, _T("{ CALL dbo.MyProc; 1(?,?) }"))
> > It all works sweet as, but it can take a while and I want to let the
> > user abort it.
> > Everything I've tried ends in tears.|||Hi

I am not sure what you mean by killing the server. Look up the KILL command
in books online.
Killing your thread should not result in the program crashing, but may leave
an orphaned process on the SQL server.

John

"Mike Brown" <browna@.beer.com> wrote in message
news:ea197978.0407011050.4a44f3c5@.posting.google.c om...
> I have the command running in a separate thread.
> I dont want to kill the server, just the CALL. I have tried killing
> the thread and using .Abort(), and most other things I can think of,
> but everything results in my program crashing.
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:<AKPEc.694$t8.6278387@.news-text.cableinet.net>...
> > Hi
> > You can issue a KILL command on the SQL Server which will terminate the
> > process. To do this you are going to need a separate thread. More
> > information in books online.
> > John
> > "Mike Brown" <browna@.beer.com> wrote in message
> > news:ea197978.0406302059.3f4b8524@.posting.google.c om...
> > > Hello
> > > > I am calling a stored procedure in a MSDE/SQLServer DB form within my
> > > Visual C++ 6.0 program along the lines
> > > CCommand<CAccessor<CdboMyAccessor>>::Open(m_session, NULL);
> > > With
> > > DEFINE_COMMAND(CdboMyAccessor, _T("{ CALL dbo.MyProc; 1(?,?) }"))
> > > It all works sweet as, but it can take a while and I want to let the
> > > user abort it.
> > > Everything I've tried ends in tears.|||John Bell (jbellnewsposts@.hotmail.com) writes:
> I am not sure what you mean by killing the server. Look up the KILL
> command in books online.

And Books Online says:

KILL permissions default to the members of the sysadmin and processadmin
fixed database roles, and are not transferable.

And Mike wants to give his users away to cancel their running commands.

And killing the entire connection would be a huge overkill anyway, when
all you want to do is to cancel the current batch.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Mike Brown (browna@.beer.com) writes:
> I am calling a stored procedure in a MSDE/SQLServer DB form within my
> Visual C++ 6.0 program along the lines
> CCommand<CAccessor<CdboMyAccessor>>::Open(m_session, NULL);
> With
> DEFINE_COMMAND(CdboMyAccessor, _T("{ CALL dbo.MyProc; 1(?,?) }"))
> It all works sweet as, but it can take a while and I want to let the
> user abort it.
> Everything I've tried ends in tears.

You don't say much of what you have tried. Then again, I will have to
admit that I have no experience of OLE DB Consumer templates, although
I've recently started to program against SQLOLEDB.

But I can't see but that to do this, you need to use asynchrounous
execution. The MDAC Books Online says:

Consumers that want to asynchronously open a rowset set the
DBPROPVAL_ASYNCH_INITIALIZE bit in the DBPROP_ROWSET_ASYNCH property.
When setting this bit prior to calling ICommand::Execute,
IOpenRowset::OpenRowset, IDBSchemaRowset::GetRowset,
IRowPosition::GetRowset, IColumnsRowset::GetColumnsRowset,
IMultipleResults::GetResult, ISourcesRowset::GetSourcesRowset, or any
other method that returns a rowset, riid must be set to
IID_IDBAsynchStatus, IID_IConnectionPointContainer, or IID_IUnknown.
...
To cancel creation of the rowset, the consumer can call
IDBAsynchStatus::Abort or can simply release all interfaces on the
rowset. Once the rowset's reference count goes to zero, any
asynchronous processing is canceled and the rowset is released. Calling
IDBAsynchStatus::Abort still requires releasing the interface.

If you don't do it asynchrounously... I guess you could start to
release things from another thread, but I'm not surprised if it ends
in tears...

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||John was referring to the T-SQL 'KILL' command, not the unix kill command.

"Mike Brown" <browna@.beer.com> wrote in message
news:ea197978.0407011050.4a44f3c5@.posting.google.c om...
> I have the command running in a separate thread.
> I dont want to kill the server, just the CALL. I have tried killing
> the thread and using .Abort(), and most other things I can think of,
> but everything results in my program crashing.
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:<AKPEc.694$t8.6278387@.news-text.cableinet.net>...
> > Hi
> > You can issue a KILL command on the SQL Server which will terminate the
> > process. To do this you are going to need a separate thread. More
> > information in books online.

Sunday, March 11, 2012

A single computer cannot connect to MSDE

I have an instance of MSDE running that have 3 computers connected to it and
using it no problems. 1 computer cannot connect or even see msde when
enumerating sql servers using sqldmo. This computer can ping the server msde
is on no problem. My thought was to next look at the netlibrary on the
server and on the client and verify both TCP and named pipes setup. Any
further suggestions on how to get this fixed would be appreciated. There is
not a firewall issue.
Thanks
Have you made sure the MDAC on that client is updated?
http://www.microsoft.com/downloads/d...displaylang=en
"Ferde" <Ferde@.discussions.microsoft.com> wrote in message
news:218DE741-04BA-4C0E-B4E3-9CF71CBED37C@.microsoft.com...
> I have an instance of MSDE running that have 3 computers connected to it
and
> using it no problems. 1 computer cannot connect or even see msde when
> enumerating sql servers using sqldmo. This computer can ping the server
msde
> is on no problem. My thought was to next look at the netlibrary on the
> server and on the client and verify both TCP and named pipes setup. Any
> further suggestions on how to get this fixed would be appreciated. There
is
> not a firewall issue.
> Thanks

A single computer cannot connect to MSDE

I have an instance of MSDE running that have 3 computers connected to it and
using it no problems. 1 computer cannot connect or even see msde when
enumerating sql servers using sqldmo. This computer can ping the server msd
e
is on no problem. My thought was to next look at the netlibrary on the
server and on the client and verify both TCP and named pipes setup. Any
further suggestions on how to get this fixed would be appreciated. There is
not a firewall issue.
ThanksHave you made sure the MDAC on that client is updated?
http://www.microsoft.com/downloads/...&displaylang=en
"Ferde" <Ferde@.discussions.microsoft.com> wrote in message
news:218DE741-04BA-4C0E-B4E3-9CF71CBED37C@.microsoft.com...
> I have an instance of MSDE running that have 3 computers connected to it
and
> using it no problems. 1 computer cannot connect or even see msde when
> enumerating sql servers using sqldmo. This computer can ping the server
msde
> is on no problem. My thought was to next look at the netlibrary on the
> server and on the client and verify both TCP and named pipes setup. Any
> further suggestions on how to get this fixed would be appreciated. There
is
> not a firewall issue.
> Thanks

Saturday, February 25, 2012

A Question Regarding MSDE Desktop Engine

Dear all,

This week I was told to setup MSDE Desktop Engine on my pc bcz my Access back end db is getting bigger in size. And as a little advance step, I decided to put my Access back end on SQL server.

To be frank, I have no experience with SQL server but after reading the instructions, I have installed MSDE (latest version) on my pc successfully. A small icon of SQL server appeared nearby clock icon of my pc showing the SQL server is running on ASHFAQUEPC.

I shifted a Trial db onto this server in following way.

Considering the opened Trial db would be my BE, from the Tools--Database Utility--Upsize wizard, I followed below steps according to Upsize wizard.

1. I selected Local server and check marked to Use Trusted Connection.
2. And then I selected some tables to export
3. Kept all default attributes of db as it is
4. Selected Let the wizard decide under data option to include.
5. At the next step What application change do you want to make?
a. Create a new Access client/Server application.
b. Link SQL Server tables to existing application.
c. No application changes. (I selected this option)

Then it showed me the report of my db description of changes that were made after deploying it. The report I did not print bcz it was a trial db with one table (2 fields) and a simple query.

My idea was to connect my Trial BE with another one of another Access mdb file so FE would be Access and BE would be from MSDE.

1. Now I dont know how to link my BE to my FE?
2. From where I can directly see my BE? Because SQL Server Service Manager does
not have any menu?
3. Where I was wrong in following steps?

Guidance in this regards is highly appreciated.

With kind regards,
AshfaqueI got it.

The tables of db from MSDE2000A I can get connected thru database project file.

Thanks.
Ashfaque

Monday, February 13, 2012

a msde question (maintenance plan)...

can one use the maintenance plan to do a scheduled backup job for a
msde (sql2k) database? i tried to do it, but there is no schedule
availalbe under the complete backup tab. thank youWhat OS are you running on?
Andrew J. Kelly SQL MVP
"=== Steve L ===" <steve.lin@.powells.com> wrote in message
news:1112997703.048071.30180@.g14g2000cwa.googlegroups.com...
> can one use the maintenance plan to do a scheduled backup job for a
> msde (sql2k) database? i tried to do it, but there is no schedule
> availalbe under the complete backup tab. thank you
>|||OS is win2k, just like other servers, except on this box, only msde for
sql was installed.|||I assume you are using enterprise manager. Are you sure you have the msde
instance registered under an account with sa privileges? Is SQL Agent
running? Other than that I don't know why it wouldn't show up.
Andrew J. Kelly SQL MVP
"=== Steve L ===" <steve.lin@.powells.com> wrote in message
news:1113232709.552087.257980@.z14g2000cwz.googlegroups.com...
> OS is win2k, just like other servers, except on this box, only msde for
> sql was installed.
>|||yes, i was running EM from the other server which has a full install of
sql2k.
the msde (and its sql agent) is running under a domain acct with sa
privileges.
i can create a scheduled backup job thru backup wizard, but am
wondering if anyone can do that thru creating a maintenance plan,
because the calendar function under the maintenance is not working, i
don't know if that's the limitation of msde since i have never dealt
with it before (i have always used the full version of sql in the
past).
thank you|||Got me too. I rarely deal with MSDE but I thought you could create a MP
with no problems.
Andrew J. Kelly SQL MVP
"=== Steve L ===" <steve.lin@.powells.com> wrote in message
news:1113255355.743242.110980@.o13g2000cwo.googlegroups.com...
> yes, i was running EM from the other server which has a full install of
> sql2k.
> the msde (and its sql agent) is running under a domain acct with sa
> privileges.
> i can create a scheduled backup job thru backup wizard, but am
> wondering if anyone can do that thru creating a maintenance plan,
> because the calendar function under the maintenance is not working, i
> don't know if that's the limitation of msde since i have never dealt
> with it before (i have always used the full version of sql in the
> past).
> thank you
>

Thursday, February 9, 2012

A few newbie questions on MSDE / Windows 2003 SBS

Hi!
I've installed a SBS 2K3 server, and everything seem to rock ok. If I not
misunderstood the whole concept, MSDE 2000 is shipped with the server OS, ok?
I've also installed Veritas BE ver. 9.1 Standard for SBS and the antivirus
software Panda Enerprise Secure. Both applications seem to register with SQL
ok, creating instances I can view by right-clicking the services icon to the
left of the system-time display.
But what if I need to create a database manually? I need to install a
dentist-application for my customer, and the installation-procedure doesn't
automatically register with sql. The database has to be moved to the new
server, and registered with sql FIRST.
What to do? Must my Customer by a full version of SQL server? Is it possible
to install SQL Server Standard Edition on a 2003 SBS ?
I would (as usual) be very grateful for any hints and tip's about this issue.
Regards
Tom Hagen
Tom,
I am not sure about registering the database manually with MSDE, as I am
still new to using it, but you can install SQL 2000 on SBS 2003. SBS2003
Premium comes with SQL Server anyway.
John
"Tom" wrote:

> Hi!
> I've installed a SBS 2K3 server, and everything seem to rock ok. If I not
> misunderstood the whole concept, MSDE 2000 is shipped with the server OS, ok?
> I've also installed Veritas BE ver. 9.1 Standard for SBS and the antivirus
> software Panda Enerprise Secure. Both applications seem to register with SQL
> ok, creating instances I can view by right-clicking the services icon to the
> left of the system-time display.
> But what if I need to create a database manually? I need to install a
> dentist-application for my customer, and the installation-procedure doesn't
> automatically register with sql. The database has to be moved to the new
> server, and registered with sql FIRST.
> What to do? Must my Customer by a full version of SQL server? Is it possible
> to install SQL Server Standard Edition on a 2003 SBS ?
> I would (as usual) be very grateful for any hints and tip's about this issue.
> Regards
> Tom Hagen
|||Hi, John!
I've managed to get some info on this issue (by MS themselves, actually).
You have to manually (by command-prompt), create an "instance" in MSDE. You
run MSDE setup with parameters (examples included in a htm-file in
installation folder).
Check out MSDE 2000 release A on:
http://www.microsoft.com/sql/msde/downloads/default.asp
I spoke to a swedish ms-consultant and he told me that installation of SQL
version 2000, 2003 or whatever is not possible on sbs 2k3 . MSDE 2000 is
tested by MS for one (1) default instance and fifteen (15) named instances.
So he and I and some programmers who developed the dental-application are
going
to give it a try.
Thanks, anyway!
Tom
"John Tkalcich" wrote:
[vbcol=seagreen]
> Tom,
> I am not sure about registering the database manually with MSDE, as I am
> still new to using it, but you can install SQL 2000 on SBS 2003. SBS2003
> Premium comes with SQL Server anyway.
> John
> "Tom" wrote: