We got our own key. but i lost this software...
My company dont' want to upgrade it.
Any people can give a help ?
The simplest way would be to contact "SnoopSoft" the company that produces
SqlExec http://www.snoopsoft.com/sqlexec/index.html
Cristian Lefter, SQL Server MVP
"Agnes" <agnes@.dynamictech.com.hk> wrote in message
news:utLx4mGVFHA.3544@.TK2MSFTNGP10.phx.gbl...
> We got our own key. but i lost this software...
> My company dont' want to upgrade it.
> Any people can give a help ?
>
|||You might mean SQLExecMS from laplas-soft, if this is the case then an
upgrade within any major version is free for that product, just ask for a
new key.
"Agnes" <agnes@.dynamictech.com.hk> wrote in message
news:utLx4mGVFHA.3544@.TK2MSFTNGP10.phx.gbl...
> We got our own key. but i lost this software...
> My company dont' want to upgrade it.
> Any people can give a help ?
>
2012年3月25日星期日
2012年2月25日星期六
Any luck?
Hi All -
Yet another company with the EXACT same problem that all of you have so
eloquently described. Was there any luck with either the application of the
patches (or SP1) mentioned or in the use of SQLXMLOLEDB as the provider?
Thanks
Keith
Hi Keith,
Could you kindly explain the problem that you are referring to?
thanks
Chandra
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
"klockwood" <klockwood@.discussions.microsoft.com> wrote in message
news:ED3DC4B7-C52A-4D93-B329-A5EE6C1D6630@.microsoft.com...
> Hi All -
> Yet another company with the EXACT same problem that all of you have so
> eloquently described. Was there any luck with either the application of
> the
> patches (or SP1) mentioned or in the use of SQLXMLOLEDB as the provider?
> Thanks
> Keith
Yet another company with the EXACT same problem that all of you have so
eloquently described. Was there any luck with either the application of the
patches (or SP1) mentioned or in the use of SQLXMLOLEDB as the provider?
Thanks
Keith
Hi Keith,
Could you kindly explain the problem that you are referring to?
thanks
Chandra
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
"klockwood" <klockwood@.discussions.microsoft.com> wrote in message
news:ED3DC4B7-C52A-4D93-B329-A5EE6C1D6630@.microsoft.com...
> Hi All -
> Yet another company with the EXACT same problem that all of you have so
> eloquently described. Was there any luck with either the application of
> the
> patches (or SP1) mentioned or in the use of SQLXMLOLEDB as the provider?
> Thanks
> Keith
Any luck?
Hi All -
Yet another company with the EXACT same problem that all of you have so
eloquently described. Was there any luck with either the application of the
patches (or SP1) mentioned or in the use of SQLXMLOLEDB as the provider?
Thanks
KeithHi Keith,
Could you kindly explain the problem that you are referring to?
thanks
Chandra
--
---
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
"klockwood" <klockwood@.discussions.microsoft.com> wrote in message
news:ED3DC4B7-C52A-4D93-B329-A5EE6C1D6630@.microsoft.com...
> Hi All -
> Yet another company with the EXACT same problem that all of you have so
> eloquently described. Was there any luck with either the application of
> the
> patches (or SP1) mentioned or in the use of SQLXMLOLEDB as the provider?
> Thanks
> Keith
Yet another company with the EXACT same problem that all of you have so
eloquently described. Was there any luck with either the application of the
patches (or SP1) mentioned or in the use of SQLXMLOLEDB as the provider?
Thanks
KeithHi Keith,
Could you kindly explain the problem that you are referring to?
thanks
Chandra
--
---
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
"klockwood" <klockwood@.discussions.microsoft.com> wrote in message
news:ED3DC4B7-C52A-4D93-B329-A5EE6C1D6630@.microsoft.com...
> Hi All -
> Yet another company with the EXACT same problem that all of you have so
> eloquently described. Was there any luck with either the application of
> the
> patches (or SP1) mentioned or in the use of SQLXMLOLEDB as the provider?
> Thanks
> Keith
Any issues with running SQL Server 2000 Standard Edt. on a 4GB server?
Hi,
we have a project where my company and another company is using the same sql
server, the problem is that the sql server crashes approximately every 3-4
days, with something that looks like memory related issues where we get the
following errors in the eventlog just before it crashes:
17120 : SQL Server could not spawn process_loginread thread.
The other company is using some COM objects (asphttp from
www.serverobjects.com) from some stored procedures to call a website(these
are called several thousand times a day) and I think that is the problem
since i can crash my own sql server and several other development sql
servers with calling this COM object through storedprocedues several
thousand times with what looks like a memory leak as sql server uses more
and more memory the more times these stored procedures are called... the
other company of course say that they have been using this product for years
without problems.
Now the other company insists that there is problems with having 4GB memory
in the server and running the standard edition of sql server 2000. We are
not using /3GB switch in boot.ini and yes we know that standard edition of
sql server can only use 2GB max.
Anyone experienced any problems like this before on a similar setup, that
too much ram will kill sql server? because i sure haven't.
Server specs:
Dual 3Ghz Xeon, 4GB ram, Mirrored Raid, HP/compaq branded server running
windows server 2003 standard edition.
SQL Server 2000 standard edition with the latest service packHi
The COM object is leaking the memory and not SQL. SQL can't control it as it
is running in process. Tell them to run the test on their machine a few
million times in a loop and watch their server fall over.
I have seen this many times and it does not matter how much RAM you have.
Regards
Mike
"T. Schmidt" wrote:
> Hi,
> we have a project where my company and another company is using the same sql
> server, the problem is that the sql server crashes approximately every 3-4
> days, with something that looks like memory related issues where we get the
> following errors in the eventlog just before it crashes:
> 17120 : SQL Server could not spawn process_loginread thread.
> The other company is using some COM objects (asphttp from
> www.serverobjects.com) from some stored procedures to call a website(these
> are called several thousand times a day) and I think that is the problem
> since i can crash my own sql server and several other development sql
> servers with calling this COM object through storedprocedues several
> thousand times with what looks like a memory leak as sql server uses more
> and more memory the more times these stored procedures are called... the
> other company of course say that they have been using this product for years
> without problems.
> Now the other company insists that there is problems with having 4GB memory
> in the server and running the standard edition of sql server 2000. We are
> not using /3GB switch in boot.ini and yes we know that standard edition of
> sql server can only use 2GB max.
> Anyone experienced any problems like this before on a similar setup, that
> too much ram will kill sql server? because i sure haven't.
> Server specs:
> Dual 3Ghz Xeon, 4GB ram, Mirrored Raid, HP/compaq branded server running
> windows server 2003 standard edition.
> SQL Server 2000 standard edition with the latest service pack
>
>
>|||I tried using another com object(w3socket www.dimac.net) that does the same
thing and called the stored procedure 100.000 times, and sql server didn't
use anymore memory during the test. I did the same thing with the com object
i suspect leaking and could see that sql servers private bytes was rising
slowly but steadily. That has to be a good indication of a leak wouldn't you
say?
I used process explorer from system internals to monitor sql server.
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:04F273D3-1FEE-4B6A-A7F8-9AC074D79ECE@.microsoft.com...
> Hi
> The COM object is leaking the memory and not SQL. SQL can't control it as
it
> is running in process. Tell them to run the test on their machine a few
> million times in a loop and watch their server fall over.
> I have seen this many times and it does not matter how much RAM you have.
> Regards
> Mike
> "T. Schmidt" wrote:
> > Hi,
> >
> > we have a project where my company and another company is using the same
sql
> > server, the problem is that the sql server crashes approximately every
3-4
> > days, with something that looks like memory related issues where we get
the
> > following errors in the eventlog just before it crashes:
> >
> > 17120 : SQL Server could not spawn process_loginread thread.
> >
> > The other company is using some COM objects (asphttp from
> > www.serverobjects.com) from some stored procedures to call a
website(these
> > are called several thousand times a day) and I think that is the problem
> > since i can crash my own sql server and several other development sql
> > servers with calling this COM object through storedprocedues several
> > thousand times with what looks like a memory leak as sql server uses
more
> > and more memory the more times these stored procedures are called... the
> > other company of course say that they have been using this product for
years
> > without problems.
> >
> > Now the other company insists that there is problems with having 4GB
memory
> > in the server and running the standard edition of sql server 2000. We
are
> > not using /3GB switch in boot.ini and yes we know that standard edition
of
> > sql server can only use 2GB max.
> >
> > Anyone experienced any problems like this before on a similar setup,
that
> > too much ram will kill sql server? because i sure haven't.
> >
> > Server specs:
> >
> > Dual 3Ghz Xeon, 4GB ram, Mirrored Raid, HP/compaq branded server running
> > windows server 2003 standard edition.
> >
> > SQL Server 2000 standard edition with the latest service pack
> >
> >
> >
> >
> >
we have a project where my company and another company is using the same sql
server, the problem is that the sql server crashes approximately every 3-4
days, with something that looks like memory related issues where we get the
following errors in the eventlog just before it crashes:
17120 : SQL Server could not spawn process_loginread thread.
The other company is using some COM objects (asphttp from
www.serverobjects.com) from some stored procedures to call a website(these
are called several thousand times a day) and I think that is the problem
since i can crash my own sql server and several other development sql
servers with calling this COM object through storedprocedues several
thousand times with what looks like a memory leak as sql server uses more
and more memory the more times these stored procedures are called... the
other company of course say that they have been using this product for years
without problems.
Now the other company insists that there is problems with having 4GB memory
in the server and running the standard edition of sql server 2000. We are
not using /3GB switch in boot.ini and yes we know that standard edition of
sql server can only use 2GB max.
Anyone experienced any problems like this before on a similar setup, that
too much ram will kill sql server? because i sure haven't.
Server specs:
Dual 3Ghz Xeon, 4GB ram, Mirrored Raid, HP/compaq branded server running
windows server 2003 standard edition.
SQL Server 2000 standard edition with the latest service packHi
The COM object is leaking the memory and not SQL. SQL can't control it as it
is running in process. Tell them to run the test on their machine a few
million times in a loop and watch their server fall over.
I have seen this many times and it does not matter how much RAM you have.
Regards
Mike
"T. Schmidt" wrote:
> Hi,
> we have a project where my company and another company is using the same sql
> server, the problem is that the sql server crashes approximately every 3-4
> days, with something that looks like memory related issues where we get the
> following errors in the eventlog just before it crashes:
> 17120 : SQL Server could not spawn process_loginread thread.
> The other company is using some COM objects (asphttp from
> www.serverobjects.com) from some stored procedures to call a website(these
> are called several thousand times a day) and I think that is the problem
> since i can crash my own sql server and several other development sql
> servers with calling this COM object through storedprocedues several
> thousand times with what looks like a memory leak as sql server uses more
> and more memory the more times these stored procedures are called... the
> other company of course say that they have been using this product for years
> without problems.
> Now the other company insists that there is problems with having 4GB memory
> in the server and running the standard edition of sql server 2000. We are
> not using /3GB switch in boot.ini and yes we know that standard edition of
> sql server can only use 2GB max.
> Anyone experienced any problems like this before on a similar setup, that
> too much ram will kill sql server? because i sure haven't.
> Server specs:
> Dual 3Ghz Xeon, 4GB ram, Mirrored Raid, HP/compaq branded server running
> windows server 2003 standard edition.
> SQL Server 2000 standard edition with the latest service pack
>
>
>|||I tried using another com object(w3socket www.dimac.net) that does the same
thing and called the stored procedure 100.000 times, and sql server didn't
use anymore memory during the test. I did the same thing with the com object
i suspect leaking and could see that sql servers private bytes was rising
slowly but steadily. That has to be a good indication of a leak wouldn't you
say?
I used process explorer from system internals to monitor sql server.
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:04F273D3-1FEE-4B6A-A7F8-9AC074D79ECE@.microsoft.com...
> Hi
> The COM object is leaking the memory and not SQL. SQL can't control it as
it
> is running in process. Tell them to run the test on their machine a few
> million times in a loop and watch their server fall over.
> I have seen this many times and it does not matter how much RAM you have.
> Regards
> Mike
> "T. Schmidt" wrote:
> > Hi,
> >
> > we have a project where my company and another company is using the same
sql
> > server, the problem is that the sql server crashes approximately every
3-4
> > days, with something that looks like memory related issues where we get
the
> > following errors in the eventlog just before it crashes:
> >
> > 17120 : SQL Server could not spawn process_loginread thread.
> >
> > The other company is using some COM objects (asphttp from
> > www.serverobjects.com) from some stored procedures to call a
website(these
> > are called several thousand times a day) and I think that is the problem
> > since i can crash my own sql server and several other development sql
> > servers with calling this COM object through storedprocedues several
> > thousand times with what looks like a memory leak as sql server uses
more
> > and more memory the more times these stored procedures are called... the
> > other company of course say that they have been using this product for
years
> > without problems.
> >
> > Now the other company insists that there is problems with having 4GB
memory
> > in the server and running the standard edition of sql server 2000. We
are
> > not using /3GB switch in boot.ini and yes we know that standard edition
of
> > sql server can only use 2GB max.
> >
> > Anyone experienced any problems like this before on a similar setup,
that
> > too much ram will kill sql server? because i sure haven't.
> >
> > Server specs:
> >
> > Dual 3Ghz Xeon, 4GB ram, Mirrored Raid, HP/compaq branded server running
> > windows server 2003 standard edition.
> >
> > SQL Server 2000 standard edition with the latest service pack
> >
> >
> >
> >
> >
2012年2月18日星期六
Any good reporting tool?
Hello!
Our company was looking for good reporting tool... and found
It is here: http://www.perpetuumsoft.com
I just want to know: Does anybody use it?
Is it worth to purchase?
Any comments on this product or good alternatives.
Thanks in advance.And what was exactly wrong with SQL RS?
"ChrisSammer" <u41467@.uwe> wrote in message news:804c3d2282f79@.uwe...
> Hello!
> Our company was looking for good reporting tool... and found
> It is here: http://www.perpetuumsoft.com
> I just want to know: Does anybody use it?
> Is it worth to purchase?
> Any comments on this product or good alternatives.
> Thanks in advance.|||This NG is about SQL Server reporting Services, which comes with its own
reporting designer (or "reporting tool" as your term?), no other
tools/alternatives can be used to generate report for SQL Server RS, AFAIK,
so far.
"ChrisSammer" <u41467@.uwe> wrote in message news:804c3d2282f79@.uwe...
> Hello!
> Our company was looking for good reporting tool... and found
> It is here: http://www.perpetuumsoft.com
> I just want to know: Does anybody use it?
> Is it worth to purchase?
> Any comments on this product or good alternatives.
> Thanks in advance.|||Good alternative - http://www.sisense.com
"ChrisSammer" <u41467@.uwe> wrote in message news:804c3d2282f79@.uwe...
> Hello!
> Our company was looking for good reporting tool... and found
> It is here: http://www.perpetuumsoft.com
> I just want to know: Does anybody use it?
> Is it worth to purchase?
> Any comments on this product or good alternatives.
> Thanks in advance.
Our company was looking for good reporting tool... and found
It is here: http://www.perpetuumsoft.com
I just want to know: Does anybody use it?
Is it worth to purchase?
Any comments on this product or good alternatives.
Thanks in advance.And what was exactly wrong with SQL RS?
"ChrisSammer" <u41467@.uwe> wrote in message news:804c3d2282f79@.uwe...
> Hello!
> Our company was looking for good reporting tool... and found
> It is here: http://www.perpetuumsoft.com
> I just want to know: Does anybody use it?
> Is it worth to purchase?
> Any comments on this product or good alternatives.
> Thanks in advance.|||This NG is about SQL Server reporting Services, which comes with its own
reporting designer (or "reporting tool" as your term?), no other
tools/alternatives can be used to generate report for SQL Server RS, AFAIK,
so far.
"ChrisSammer" <u41467@.uwe> wrote in message news:804c3d2282f79@.uwe...
> Hello!
> Our company was looking for good reporting tool... and found
> It is here: http://www.perpetuumsoft.com
> I just want to know: Does anybody use it?
> Is it worth to purchase?
> Any comments on this product or good alternatives.
> Thanks in advance.|||Good alternative - http://www.sisense.com
"ChrisSammer" <u41467@.uwe> wrote in message news:804c3d2282f79@.uwe...
> Hello!
> Our company was looking for good reporting tool... and found
> It is here: http://www.perpetuumsoft.com
> I just want to know: Does anybody use it?
> Is it worth to purchase?
> Any comments on this product or good alternatives.
> Thanks in advance.
2012年2月13日星期一
Any compatibility issues between SQL 2005 Express and SQL 2005 Server
Hi All,
The IP company that host my site is installing SQL 2005 soon and I my building a web application with SQL 2005 Express. So the question is has anyone heard of any problems with uploading an 2005 express onto a sql 2005 server? I would like to find out now before I finish all of the work. Don't want to find out later that you can't run a sql 2005 express database on a sql 2005 server.
Thanks for taking the time to read this.
Well it seem no one know the answer so I emailed the author of a book called Beginning SQL Server 2005 Express. He emailed me back
SQL Server 2005 Express uses .mdf and .ldf file formats that are compatible with SQL Server 2005. Therefore, if you can upload the .mdf and .ldf files for your SQL Server Express database, you or your isp should be able to attach the files to their SQL Server 2005 database server.
I hope this reply helps.
Rick Dobson
So yes you should beable to upload 2005 express onto a SQL Server 2005.
Thanks away guys
Have a good day
Freon22
Any books that explain how to setup Windows 2003 Server + SQL Server 2000?
My uncle runs a small networking company and has extra licenses for Windows 2003 Server as well as SQL Server 2000. Since I just graduated from college and have started working as a database programmer (for a different company) I'd like to setup a small server at home to learn more about SQL (as well as networking, but SQL is my primary concern). I know I can setup SQL Server 2000 on my main PC, but I'd still like to set everything up in a server environment.
So, what I'm wondering is if any books (or web sites?) exist that walk you through setting up Windows 2003 Server and SQL Server 2000. I've actually set these up before (it's not very complicated) but I'm not sure if I did it the "correct" way.
Ideally if any books exist on O'Reilly's Safari Bookshelf that would be even better.
Thanks in advance,
John1. install windows 2003.
2. install sql 2000. ignor warning.
3. install sql 2000 sp3.
your done.|||double post delete|||Thanks for the reply!
The service pack (3a is most recent I believe) gets a little confusing because there are three parts:
Sql2ksp3.exe. Updates for database components.
Sql2kasp3.exe. Updates for Analysis Services components.
Sql2kdesksp3.exe. Updates for Microsoft SQL Server 2000 Desktop Engine (MSDE 2000).
Do I need to install all three parts of the service pack?
Anything else I need to do?
Thanks,
John|||You just need to update the database components. I usually get rid of the sample data (northwind and pubs) when I do a new install but since you're testing you might as well play with those.
So, what I'm wondering is if any books (or web sites?) exist that walk you through setting up Windows 2003 Server and SQL Server 2000. I've actually set these up before (it's not very complicated) but I'm not sure if I did it the "correct" way.
Ideally if any books exist on O'Reilly's Safari Bookshelf that would be even better.
Thanks in advance,
John1. install windows 2003.
2. install sql 2000. ignor warning.
3. install sql 2000 sp3.
your done.|||double post delete|||Thanks for the reply!
The service pack (3a is most recent I believe) gets a little confusing because there are three parts:
Sql2ksp3.exe. Updates for database components.
Sql2kasp3.exe. Updates for Analysis Services components.
Sql2kdesksp3.exe. Updates for Microsoft SQL Server 2000 Desktop Engine (MSDE 2000).
Do I need to install all three parts of the service pack?
Anything else I need to do?
Thanks,
John|||You just need to update the database components. I usually get rid of the sample data (northwind and pubs) when I do a new install but since you're testing you might as well play with those.
订阅：
博文 (Atom)