No longer need default instance of SQL Server

Currently I have a server that has two instances of SQL Server that are
both heavily used. We are moving the databases that are on the default
instance of this server to a new server. Since the old server will
only need one instance (the current named instance) of SQL Server is
there a good way to remove the default instance and make the named
instance the default? If this change is possible will the name of the
current named instance need to be changed? Will all of the programs
currently accessing the named instance need to change their connection
string?AJ (ablanchard@.mnlife.com) writes:
> Currently I have a server that has two instances of SQL Server that are
> both heavily used. We are moving the databases that are on the default
> instance of this server to a new server. Since the old server will
> only need one instance (the current named instance) of SQL Server is
> there a good way to remove the default instance and make the named
> instance the default? If this change is possible will the name of the
> current named instance need to be changed? Will all of the programs
> currently accessing the named instance need to change their connection
> string?

You could uninstall the default instance and keep the named instance
as it is. To be honest, I have not actually tried it, but I am quite
convinced that it is possible.

I don't see the point with making the named instance the default
instance, not the least if you would have to go and change
connection strings.

And I don't think there is a simple way to rename an instance. Probably
the easiest method would be to detach the databases, and attach them
to the existing default instance. If you really want to have them a
default instance, that is.

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

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Thanks for your suggestion. I guess I just thought there had to be a
default instance. In a test environment I created a default and a
named instance and then removed the default instance and everthing
seemed to be fine. It seems this will be my solution.

AJ

No Local instance with SQLServer2005 Dev. Ed.

(New to SQL Server Installs)

I installed SQL Server 2005 Developer Edition on a WinXP-SP2
workstation and can see some enterprise databases on the network just
fine.

My problem is I cannot register a local database on the local drive for
testing/education purposes.
(I accepted all of the defaults on the install and thought all was
well.)

There are a couple of small databases that are in development in our
group and I need to work on when offline from the network.

Short of uninstalling the whole product and doing it over, what steps
can I take to remedy this so I will be able to work with DB's locally?

Thanks.My problem is I cannot register a local database on the local drive for

Quote:

Originally Posted by

testing/education purposes.

I'm not sure what you mean by 'register' a local database. A database can
be created with CREATE DATABASE (including attach) or RESTORE.

Quote:

Originally Posted by

There are a couple of small databases that are in development in our
group and I need to work on when offline from the network.

I suggest you create a backup of the desired databases and then restore.
You can use SQL Server Management Studio for this.

--
Hope this helps.

Dan Guzman
SQL Server MVP

"RLN" <rlntemp-newsgroup@.yahoo.comwrote in message
news:1161270087.986650.261700@.b28g2000cwb.googlegr oups.com...

Quote:

Originally Posted by

(New to SQL Server Installs)
>
I installed SQL Server 2005 Developer Edition on a WinXP-SP2
workstation and can see some enterprise databases on the network just
fine.
>
My problem is I cannot register a local database on the local drive for
testing/education purposes.
(I accepted all of the defaults on the install and thought all was
well.)
>
There are a couple of small databases that are in development in our
group and I need to work on when offline from the network.
>
Short of uninstalling the whole product and doing it over, what steps
can I take to remedy this so I will be able to work with DB's locally?
>
Thanks.
>

|||Dan,
Please accept my 2 apologies; first for a late reply, and second if I
am using SQL-Server terms incorrectly.

On a 2nd test box (WinXP-SP2) I have Sql Server 2005 Developer Edition
installed.

What works:
-When I launch Mgmt Studio, I am able to connect to an enterprise SQL
Server box successfully on our network.
-In Mgmt Studio, when I click on "View/Registered Servers", I can see
"W4082107/test". This is my test box. I am under the impression that
"W4082107/test" is a "local" SQL Server where I can copy sample
databases off of the network and compose and work with copies of
Northwind, etc.

What does not work:
-I am not able to have a local instance of SQL server working on my
local drive to do some practice work with SQL Server.

I'll take a look on MSDN, TechNet and the MSKB for a page (maybe a
'step-by-step') that references setting up a local instance of SQL
Server when it is working with the Enterprise servers just fine. I
thought I could install SQLServer Express to get my local databases to
work, but MS says the Developer Edition and Express cannot exist on the
same box.

I hope this clarifies my original request.

Dan Guzman wrote:

Quote:

Originally Posted by

Quote:

Originally Posted by

My problem is I cannot register a local database on the local drive for
testing/education purposes.

>
I'm not sure what you mean by 'register' a local database. A database can
be created with CREATE DATABASE (including attach) or RESTORE.
>

Quote:

Originally Posted by

There are a couple of small databases that are in development in our
group and I need to work on when offline from the network.

>
I suggest you create a backup of the desired databases and then restore.
You can use SQL Server Management Studio for this.
>
--
Hope this helps.
>
Dan Guzman
SQL Server MVP
>
"RLN" <rlntemp-newsgroup@.yahoo.comwrote in message
news:1161270087.986650.261700@.b28g2000cwb.googlegr oups.com...

Quote:

Originally Posted by

(New to SQL Server Installs)

I installed SQL Server 2005 Developer Edition on a WinXP-SP2
workstation and can see some enterprise databases on the network just
fine.

My problem is I cannot register a local database on the local drive for
testing/education purposes.
(I accepted all of the defaults on the install and thought all was
well.)

There are a couple of small databases that are in development in our
group and I need to work on when offline from the network.

Short of uninstalling the whole product and doing it over, what steps
can I take to remedy this so I will be able to work with DB's locally?

Thanks.

|||RLN (rlntemp-newsgroup@.yahoo.com) writes:

Quote:

Originally Posted by

On a 2nd test box (WinXP-SP2) I have Sql Server 2005 Developer Edition
installed.
>
What works:
-When I launch Mgmt Studio, I am able to connect to an enterprise SQL
Server box successfully on our network.
-In Mgmt Studio, when I click on "View/Registered Servers", I can see
"W4082107/test". This is my test box. I am under the impression that
"W4082107/test" is a "local" SQL Server where I can copy sample
databases off of the network and compose and work with copies of
Northwind, etc.

Yes and no. You can backup a database on the big SQL Server, and
restore the database on your machine. But this presumes that there
is a network share somewhere, but both you and SQL Server can access.

You can also use the Copy Database Wizard to copy a database with the
SMO method, which copies the database object by object. But CDW is
very buggy, and may not copy everything.

Quote:

Originally Posted by

What does not work:
-I am not able to have a local instance of SQL server working on my
local drive to do some practice work with SQL Server.

In what way does it not work? Since you provide no information, I
will ask a couple of basic questions:

* You are certain that you installed the Database Engine and not just
only the tools?
* If so, have you ensured that SQL Server is running? Check this in the
SQL Configuration Manager.
* If it is running, do you connect to it properly. I assume that W4082107
is your workstation. The /test should probably be \test, if you have
installed SQL 2005 as a named instance. You can view the instance
names in the Configuration Manager.

Quote:

Originally Posted by

I'll take a look on MSDN, TechNet and the MSKB for a page (maybe a
'step-by-step') that references setting up a local instance of SQL
Server when it is working with the Enterprise servers just fine. I
thought I could install SQLServer Express to get my local databases to
work, but MS says the Developer Edition and Express cannot exist on the
same box.

That is not correct. It's perfectly possible to have instance of both
Developer and Expres Edition on the same box. What is not possible is
to install SQL Server Management Studio Express if you have the big
Mgmt Studio installed and vice versa.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspxsql

No instance of SQL Server under MSDE installation

Hi all,
after successfully completing the installation of a
downloaded copy of MSDE for VS.Net things are
not working at all.
I was having trouble with my VS.Net installation so I
uninstalled VS.Net and MSDE.
I have installed MSDE several times today and each
time I can not see the instance name of the installation.
I have removed any existing directories, cleared the
obvious things from the registry, changed the instance
name and even chosen different target and data
directories to try and solve the problem. The service
seems to have started correctly, but I do not get
a green play icon in the system tray at the bottom of
the screen. When i open the server manager I
can not see the server running at all.
I do not know what to do next. Does anyone have any
ideas as to what what be causing this problem?
Many thanks for your assistance in helping me to
solve this problem.
Regards,
Jason.
Please ignore this post. I was just to impatient to wait
for all the services, etc to start.
All appears to be OK now.
Thanks.
On Thu, 29 Apr 2004 18:40:13 +0100, JJ <jason@.nospam.divemaster.org>
wrote:

>Hi all,
>after successfully completing the installation of a
>downloaded copy of MSDE for VS.Net things are
>not working at all.
>I was having trouble with my VS.Net installation so I
>uninstalled VS.Net and MSDE.
>I have installed MSDE several times today and each
>time I can not see the instance name of the installation.
>I have removed any existing directories, cleared the
>obvious things from the registry, changed the instance
>name and even chosen different target and data
>directories to try and solve the problem. The service
>seems to have started correctly, but I do not get
>a green play icon in the system tray at the bottom of
>the screen. When i open the server manager I
>can not see the server running at all.
>I do not know what to do next. Does anyone have any
>ideas as to what what be causing this problem?
>Many thanks for your assistance in helping me to
>solve this problem.
>Regards,
>Jason.

No Default SQL Instance on Install?

Problem: When the application installs it requires SQL Express Server 2005. If it does not exist it will install it or rollback. -> continue installation -> When the form attempts to locate an SQL Instance on a machine that has not had SQL server or any components connected before it shows up as <null>. I need to have access to the server(s) instances in order to build the application database inside SQL. Am I using the wrong approach with SQLDMO? Is there adifferent method to access the installed SQL Express 2005 connection string?
Current code to locate SQL Instances:
try
{
////////////////////////////////////////
// Search and List SQL Server Instances
////////////////////////////////////////
//set cursor to thinking/hourglass
System.Windows.Forms.Cursor.Current = System.Windows.Forms.Cursors.AppStarting;
//begin
ArrayList aServers = new ArrayList();
SQLDMO.ApplicationClass acServers = new SQLDMO.ApplicationClass();
//loop through the servers found
for (int iServerGroupCount = 1; iServerGroupCount <= acServers.ServerGroups.Count; iServerGroupCount++)
{
for (int iServerCount = 1; iServerCount <= acServers.ServerGroups.Item(iServerGroupCount).RegisteredServers.Count; iServerCount++)
{
aServers.Add(acServers.ServerGroups.Item(iServerGroupCount).RegisteredServers.Item(iServerCount).Name);
}
}
//add the servers to the drop down box
if (aServers.Count < 1)
{
string NotExist = "<No Servers Found>";
cboServers.Items.Add(NotExist);

cboServers.SelectedIndex = 0;
btnSQLDataBaseCheckDB.Enabled = false;

}
else
{
cboServers.Items.AddRange(aServers.ToArray());
//select the first item in the array index to display
cboServers.SelectedIndex = 0;
}
}
catch (Exception ServerException)
{
MessageBox.Show(ServerException.Message);
}

Slightly stuck at the moment with this. Any tips or leads in the right direction would be greatly appreciated.
sorry to double post. Found a relative link in the forums which may add some more insight to the problem, though certainly not solve it.
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=385579&SiteID=1&mode=1

No "Maintenance Plans" under SQL Server 2005

Running "SQL Server Mgmt Studio"
For the software "SQL Server 2005"
Under the SERVER instance, there's Mgmt -> Maint Plans.
Under SERVER\INSTANCE, there's no Maintenance Plans.
The DBs I need to back up are under SERVER\INSTANCE.
Any idea why my server instance does not have the option?
Thanks,
ScottThere are none by default, you have to create them. Right click and say "New
Maintenance Plan" or choose the wizard.
--
Andrew J. Kelly SQL MVP
"Scott Moseman" <scmoseman@.gmail.com> wrote in message
news:1157491039.842488.194100@.m79g2000cwm.googlegroups.com...
> Running "SQL Server Mgmt Studio"
> For the software "SQL Server 2005"
> Under the SERVER instance, there's Mgmt -> Maint Plans.
> Under SERVER\INSTANCE, there's no Maintenance Plans.
> The DBs I need to back up are under SERVER\INSTANCE.
> Any idea why my server instance does not have the option?
> Thanks,
> Scott
>|||Scott Moseman wrote:
> Running "SQL Server Mgmt Studio"
> For the software "SQL Server 2005"
> Under the SERVER instance, there's Mgmt -> Maint Plans.
> Under SERVER\INSTANCE, there's no Maintenance Plans.
> The DBs I need to back up are under SERVER\INSTANCE.
> Any idea why my server instance does not have the option?
> Thanks,
> Scott
>
Skip the maintenance plan and use a scheduled T-SQL script to do your
backups. See
http://realsqlguy.com/serendipity/archives/11-Send-In-Backup!.html for a
script that will backup every database on your server, all you have to
do is schedule it to run.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||I'm not talking about it missing a maintenance plan, I'm talking
about the Management folder not even having the Maintenance
Plan subfolder under which you'd add any new plans. Adding a
maintenance plan is not a problem, but there's no place to do it.
Thanks,
Scott
Andrew J. Kelly wrote:
> There are none by default, you have to create them. Right click
> and say "New Maintenance Plan" or choose the wizard.
> --
> Andrew J. Kelly SQL MVP
>
> "Scott Moseman" <scmoseman@.gmail.com> wrote:
> > Running "SQL Server Mgmt Studio"
> > For the software "SQL Server 2005"
> >
> > Under the SERVER instance, there's Mgmt -> Maint Plans.
> > Under SERVER\INSTANCE, there's no Maintenance Plans.
> >
> > The DBs I need to back up are under SERVER\INSTANCE.
> > Any idea why my server instance does not have the option?
> >
> > Thanks,
> > Scott
> >|||Hi,
I had the same problem.
You need to install Integration Services also for that instance
SERVER\INSTANCE.
HTH
Flor
Tracy McKibben a =E9crit :
> Scott Moseman wrote:
> > Running "SQL Server Mgmt Studio"
> > For the software "SQL Server 2005"
> >
> > Under the SERVER instance, there's Mgmt -> Maint Plans.
> > Under SERVER\INSTANCE, there's no Maintenance Plans.
> >
> > The DBs I need to back up are under SERVER\INSTANCE.
> > Any idea why my server instance does not have the option?
> >
> > Thanks,
> > Scott
> >
> Skip the maintenance plan and use a scheduled T-SQL script to do your
> backups. See
> http://realsqlguy.com/serendipity/archives/11-Send-In-Backup!.html for a
> script that will backup every database on your server, all you have to
> do is schedule it to run.
> > > -- > Tracy McKibben
> MCDBA
> http://www.realsqlguy.com

No "Maintenance Plans" under SQL Server 2005

Running "SQL Server Mgmt Studio"
For the software "SQL Server 2005"
Under the SERVER instance, there's Mgmt -> Maint Plans.
Under SERVER\INSTANCE, there's no Maintenance Plans.
The DBs I need to back up are under SERVER\INSTANCE.
Any idea why my server instance does not have the option?
Thanks,
ScottThere are none by default, you have to create them. Right click and say "New
Maintenance Plan" or choose the wizard.
Andrew J. Kelly SQL MVP
"Scott Moseman" <scmoseman@.gmail.com> wrote in message
news:1157491039.842488.194100@.m79g2000cwm.googlegroups.com...
> Running "SQL Server Mgmt Studio"
> For the software "SQL Server 2005"
> Under the SERVER instance, there's Mgmt -> Maint Plans.
> Under SERVER\INSTANCE, there's no Maintenance Plans.
> The DBs I need to back up are under SERVER\INSTANCE.
> Any idea why my server instance does not have the option?
> Thanks,
> Scott
>|||Scott Moseman wrote:
> Running "SQL Server Mgmt Studio"
> For the software "SQL Server 2005"
> Under the SERVER instance, there's Mgmt -> Maint Plans.
> Under SERVER\INSTANCE, there's no Maintenance Plans.
> The DBs I need to back up are under SERVER\INSTANCE.
> Any idea why my server instance does not have the option?
> Thanks,
> Scott
>
Skip the maintenance plan and use a scheduled T-SQL script to do your
backups. See
http://realsqlguy.com/serendipity/a...-Send-In-Backup!.html for a
script that will backup every database on your server, all you have to
do is schedule it to run.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||I'm not talking about it missing a maintenance plan, I'm talking
about the Management folder not even having the Maintenance
Plan subfolder under which you'd add any new plans. Adding a
maintenance plan is not a problem, but there's no place to do it.
Thanks,
Scott
Andrew J. Kelly wrote:[vbcol=seagreen]
> There are none by default, you have to create them. Right click
> and say "New Maintenance Plan" or choose the wizard.
> --
> Andrew J. Kelly SQL MVP
>
> "Scott Moseman" <scmoseman@.gmail.com> wrote:
>|||Hi,
I had the same problem.
You need to install Integration Services also for that instance
SERVER\INSTANCE.
HTH
Flor
Tracy McKibben a =E9crit :

> Scott Moseman wrote:
> Skip the maintenance plan and use a scheduled T-SQL script to do your
> backups. See
> http://realsqlguy.com/serendipity/a...-Send-In-Backup!.html for a
> script that will backup every database on your server, all you have to
> do is schedule it to run.
>=20
>=20
> --=20
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com

Newbie: MSDE no longer listens to outside request. Event id 19011.

Hi
I've had a MSDE 2000 instance running a couple of months without any
problems. Now all of a sudden I can only connect to it from localhost.
When I restart the sql-server using the Service Manager it gives a
warning in the event log with event-ID 19011. Error code 1355.
Also I have a bunch of informational events with event-id 3 and
something about some missing file. I'm not sure if the two event-types
have something to do with each other, though.
I believe my problems started after installing a very simple program
called Dyndns Updater. Looking in the install-log I found that it only
installs the main exe, some txt-files and a normal run-parameter in the
registry. To me it seems unlikely that it should interfere with MSDE in
any way. Uninstalling doesn't help either.
All other services on my server are working normally from another computer.
I'm kind of stuck here, not wanting to uninstall/reinstall MSDE.
Any pointers?
Regards
dne Hovda
GTR AS
NORWAY
Michael C# wrote:
> How about firewalls? Are you running MSDE on Win XP and have you installed
> SP 2 recently? The Windows Firewall will, by default, prevent responses to
> inbound traffic from Ports 1433 (TCP) and 1434 (UDP). If this is your
> problem, try opening up these two ports on your Windows Firewall.
Sorry, I forgot to specify.
We have a pretty simple network of 6 machines, no internal firewalls.
MSDE runs on W2KSP4. I've tried both with and without firewall on the
client-machines that all run XPSP2. It doesn't seem to be a
firewall-related problem. Also, I checked that IP-filtering is turned
off on the server.
Looking deeper into the logs, I found that the program I before
mentioned has definetely nothing to do with it, as I see the same error
(19011) at least two more times, exactly one and two weeks ago, to be
specific.
dne
|||Chris V. wrote:
> What is the size of the MDF file, or the LDF ?
> If I remember properly, the max size is 2Gb, and if I am still right, the
> 2Gb apply to the physical file, to the size of the active pages.
The total size of all databases in the instance is 58MB...
This is very strange: All of a sudden it just started working again! I
can now connect from all clients. I haven't changed anything.
Hm. This problem might not be MSDE related after all. Still I'm
wondering what those error messages mean, though.
Anyway, thanks for your help, guys.
dne

Newbie: MSDE no longer listens to outside request. Event id 19011.

Hi
I've had a MSDE 2000 instance running a couple of months without any
problems. Now all of a sudden I can only connect to it from localhost.
When I restart the sql-server using the Service Manager it gives a
warning in the event log with event-ID 19011. Error code 1355.
Also I have a bunch of informational events with event-id 3 and
something about some missing file. I'm not sure if the two event-types
have something to do with each other, though.
I believe my problems started after installing a very simple program
called Dyndns Updater. Looking in the install-log I found that it only
installs the main exe, some txt-files and a normal run-parameter in the
registry. To me it seems unlikely that it should interfere with MSDE in
any way. Uninstalling doesn't help either.
All other services on my server are working normally from another computer.
I'm kind of stuck here, not wanting to uninstall/reinstall MSDE.
Any pointers?
Regards
dne Hovda
GTR AS
NORWAYMichael C# wrote:
> How about firewalls? Are you running MSDE on Win XP and have you installe
d
> SP 2 recently? The Windows Firewall will, by default, prevent responses t
o
> inbound traffic from Ports 1433 (TCP) and 1434 (UDP). If this is your
> problem, try opening up these two ports on your Windows Firewall.
Sorry, I forgot to specify.
We have a pretty simple network of 6 machines, no internal firewalls.
MSDE runs on W2KSP4. I've tried both with and without firewall on the
client-machines that all run XPSP2. It doesn't seem to be a
firewall-related problem. Also, I checked that IP-filtering is turned
off on the server.
Looking deeper into the logs, I found that the program I before
mentioned has definetely nothing to do with it, as I see the same error
(19011) at least two more times, exactly one and two weeks ago, to be
specific.
dne|||Chris V. wrote:
> What is the size of the MDF file, or the LDF ?
> If I remember properly, the max size is 2Gb, and if I am still right, the
> 2Gb apply to the physical file, to the size of the active pages.
The total size of all databases in the instance is 58MB...
This is very strange: All of a sudden it just started working again! I
can now connect from all clients. I haven't changed anything.
Hm. This problem might not be MSDE related after all. Still I'm
wondering what those error messages mean, though.
Anyway, thanks for your help, guys.
dne

Newbie: MSDE no longer listens to outside request. Event id 19011.

Hi
I've had a MSDE 2000 instance running a couple of months without any
problems. Now all of a sudden I can only connect to it from localhost.
When I restart the sql-server using the Service Manager it gives a
warning in the event log with event-ID 19011. Error code 1355.
Also I have a bunch of informational events with event-id 3 and
something about some missing file. I'm not sure if the two event-types
have something to do with each other, though.
I believe my problems started after installing a very simple program
called Dyndns Updater. Looking in the install-log I found that it only
installs the main exe, some txt-files and a normal run-parameter in the
registry. To me it seems unlikely that it should interfere with MSDE in
any way. Uninstalling doesn't help either.
All other services on my server are working normally from another computer.
I'm kind of stuck here, not wanting to uninstall/reinstall MSDE.
Any pointers?
Regards
Ådne Hovda
GTR AS
NORWAYHow about firewalls? Are you running MSDE on Win XP and have you installed
SP 2 recently? The Windows Firewall will, by default, prevent responses to
inbound traffic from Ports 1433 (TCP) and 1434 (UDP). If this is your
problem, try opening up these two ports on your Windows Firewall.
Thx
"Ådne Hovda" <aadne@.hovda.no> wrote in message
news:eK4kSdRFFHA.392@.TK2MSFTNGP14.phx.gbl...
> Hi
> I've had a MSDE 2000 instance running a couple of months without any
> problems. Now all of a sudden I can only connect to it from localhost.
> When I restart the sql-server using the Service Manager it gives a warning
> in the event log with event-ID 19011. Error code 1355.
> Also I have a bunch of informational events with event-id 3 and something
> about some missing file. I'm not sure if the two event-types have
> something to do with each other, though.
> I believe my problems started after installing a very simple program
> called Dyndns Updater. Looking in the install-log I found that it only
> installs the main exe, some txt-files and a normal run-parameter in the
> registry. To me it seems unlikely that it should interfere with MSDE in
> any way. Uninstalling doesn't help either.
> All other services on my server are working normally from another
> computer.
> I'm kind of stuck here, not wanting to uninstall/reinstall MSDE.
> Any pointers?
> Regards
> Ådne Hovda
> GTR AS
> NORWAY|||Michael C# wrote:
> How about firewalls? Are you running MSDE on Win XP and have you installed
> SP 2 recently? The Windows Firewall will, by default, prevent responses to
> inbound traffic from Ports 1433 (TCP) and 1434 (UDP). If this is your
> problem, try opening up these two ports on your Windows Firewall.
Sorry, I forgot to specify.
We have a pretty simple network of 6 machines, no internal firewalls.
MSDE runs on W2KSP4. I've tried both with and without firewall on the
client-machines that all run XPSP2. It doesn't seem to be a
firewall-related problem. Also, I checked that IP-filtering is turned
off on the server.
Looking deeper into the logs, I found that the program I before
mentioned has definetely nothing to do with it, as I see the same error
(19011) at least two more times, exactly one and two weeks ago, to be
specific.
Ådne|||What is the size of the MDF file, or the LDF ?
If I remember properly, the max size is 2Gb, and if I am still right, the
2Gb apply to the physical file, to the size of the active pages.
Chris
"Ådne Hovda" <aadne@.hovda.no> a écrit dans le message de news:
eFSW7zRFFHA.1564@.TK2MSFTNGP09.phx.gbl...
> Michael C# wrote:
>> How about firewalls? Are you running MSDE on Win XP and have you
>> installed SP 2 recently? The Windows Firewall will, by default, prevent
>> responses to inbound traffic from Ports 1433 (TCP) and 1434 (UDP). If
>> this is your problem, try opening up these two ports on your Windows
>> Firewall.
> Sorry, I forgot to specify.
> We have a pretty simple network of 6 machines, no internal firewalls.
> MSDE runs on W2KSP4. I've tried both with and without firewall on the
> client-machines that all run XPSP2. It doesn't seem to be a
> firewall-related problem. Also, I checked that IP-filtering is turned off
> on the server.
> Looking deeper into the logs, I found that the program I before mentioned
> has definetely nothing to do with it, as I see the same error (19011) at
> least two more times, exactly one and two weeks ago, to be specific.
> Ådne|||Chris V. wrote:
> What is the size of the MDF file, or the LDF ?
> If I remember properly, the max size is 2Gb, and if I am still right, the
> 2Gb apply to the physical file, to the size of the active pages.
The total size of all databases in the instance is 58MB...
This is very strange: All of a sudden it just started working again! I
can now connect from all clients. I haven't changed anything.
Hm. This problem might not be MSDE related after all. Still I'm
wondering what those error messages mean, though.
Anyway, thanks for your help, guys.
Ådne