Showing posts with label installation. Show all posts
Showing posts with label installation. Show all posts

Thursday, March 29, 2012

Does SQL Server save any metadata in registry or home folder?

I have my SQL Server installation on drive c: and the databases on another
drive. My c drive got corrupted and I am planning to restore it from an old
backup. This means drive c will not be up to date.

Is there anything that SQL Server saves in the registry or in its home
folder that changes frequently? I am hoping that nothing does which means
the old backup will be good enough.

Although I think the default databases are in the c drive, I will try to
get them back from a recent backup.

John DalbergHi

SQL Server does use the registry, but the locations of the user databases
are not held there. If you don't have any databases on the C drive then you
could just install the software again, service pack it, and then re-attach
the mdf and ldf files see http://support.microsoft.com/kb/224071/ for more
information. If you don't restore master then you will need to recreate the
logins and then reconcile the orphaned users
http://support.microsoft.com/kb/274188/. If you don't restore msdb you will
need to re-create jobs, dts packages etc.

If you do restore the C drive, then you could use the installation option
that allows you to rebuild the registry to specify new locations.

John

"John Dalberg" <nospam@.nospam.sss> wrote in message
news:20060115041931.065$4x@.newsreader.com...
>I have my SQL Server installation on drive c: and the databases on another
> drive. My c drive got corrupted and I am planning to restore it from an
> old
> backup. This means drive c will not be up to date.
> Is there anything that SQL Server saves in the registry or in its home
> folder that changes frequently? I am hoping that nothing does which means
> the old backup will be good enough.
> Although I think the default databases are in the c drive, I will try to
> get them back from a recent backup.
> John Dalberg

Tuesday, March 27, 2012

Does Sql Server 2005 Installation create a default instance?

Hello everybody!

I have recently installed Sql Server 2005 Enterprise Edition on my PC and I have noticed that it has not installed a default instance. I have tried to do this several times even in some other PC but no default instance is installed.

I can get a default instance if I install Sql Server 2000 but this is not the same I guess. Is there any way to install the default instance via Sql Server 2005?

Do you have already a SQL Server instance installed on the system ?

Jens K. Suessmeyer

http://www.sqlserver2005.de

|||

Are u able to install Named Instance? if not Check the OS. Enterprise Edition need Server Version of OS. Otherwise u can only install client component.

Madhu

|||Well, as I mentioned before I have installed Sql Server 2005 in several computers but I can explain you some of the cases:
1. In my computer I had already installed Sql Server 2000 and I had created two other instances except the default instance (LOCAL). Then I installed Sql Server 2005.
As a matter of fact I want to make a web synchronization for a merge replication. But I can not configure the merge replication for web synchronization because the database and its instance seems to be in SQL server 2000. That's why I want an 2005 sql server instance.

2. I have also uninstalled Sql Server 2000 and all of its instances from my computer, and I have reinstalled Sql Server 2005. But no default instance was created.

3. I have also installes Sql Server 2005 in another PC which had no instace installed, but the results were the same.

What should I do?

|||Do you mean I can not create any instance if my OS is Windows XP?
|||

Yes if you are installing Enterprise Edition it will not install Services on Windows XP. You can install Standard or any other Edition

http://www.microsoft.com/sql/editions/enterprise/sysreqs.mspx

Madhu

|||Thank U

Does Sql Server 2005 Installation create a default instance?

Hello everybody!

I have recently installed Sql Server 2005 Enterprise Edition on my PC and I have noticed that it has not installed a default instance. I have tried to do this several times even in some other PC but no default instance is installed.

I can get a default instance if I install Sql Server 2000 but this is not the same I guess. Is there any way to install the default instance via Sql Server 2005?

Do you have already a SQL Server instance installed on the system ?

Jens K. Suessmeyer

http://www.sqlserver2005.de

|||

Are u able to install Named Instance? if not Check the OS. Enterprise Edition need Server Version of OS. Otherwise u can only install client component.

Madhu

|||Well, as I mentioned before I have installed Sql Server 2005 in several computers but I can explain you some of the cases:
1. In my computer I had already installed Sql Server 2000 and I had created two other instances except the default instance (LOCAL). Then I installed Sql Server 2005.
As a matter of fact I want to make a web synchronization for a merge replication. But I can not configure the merge replication for web synchronization because the database and its instance seems to be in SQL server 2000. That's why I want an 2005 sql server instance.

2. I have also uninstalled Sql Server 2000 and all of its instances from my computer, and I have reinstalled Sql Server 2005. But no default instance was created.

3. I have also installes Sql Server 2005 in another PC which had no instace installed, but the results were the same.

What should I do?

|||Do you mean I can not create any instance if my OS is Windows XP?
|||

Yes if you are installing Enterprise Edition it will not install Services on Windows XP. You can install Standard or any other Edition

http://www.microsoft.com/sql/editions/enterprise/sysreqs.mspx

Madhu

|||Thank U

Does Sql Server 2005 Installation create a default instance?

Hello everybody!

I have recently installed Sql Server 2005 Enterprise Edition on my PC and I have noticed that it has not installed a default instance. I have tried to do this several times even in some other PC but no default instance is installed.

I can get a default instance if I install Sql Server 2000 but this is not the same I guess. Is there any way to install the default instance via Sql Server 2005?

Do you have already a SQL Server instance installed on the system ?

Jens K. Suessmeyer

http://www.sqlserver2005.de

|||

Are u able to install Named Instance? if not Check the OS. Enterprise Edition need Server Version of OS. Otherwise u can only install client component.

Madhu

|||Well, as I mentioned before I have installed Sql Server 2005 in several computers but I can explain you some of the cases:
1. In my computer I had already installed Sql Server 2000 and I had created two other instances except the default instance (LOCAL). Then I installed Sql Server 2005.
As a matter of fact I want to make a web synchronization for a merge replication. But I can not configure the merge replication for web synchronization because the database and its instance seems to be in SQL server 2000. That's why I want an 2005 sql server instance.

2. I have also uninstalled Sql Server 2000 and all of its instances from my computer, and I have reinstalled Sql Server 2005. But no default instance was created.

3. I have also installes Sql Server 2005 in another PC which had no instace installed, but the results were the same.

What should I do?

|||Do you mean I can not create any instance if my OS is Windows XP?
|||

Yes if you are installing Enterprise Edition it will not install Services on Windows XP. You can install Standard or any other Edition

http://www.microsoft.com/sql/editions/enterprise/sysreqs.mspx

Madhu

|||Thank U
sql

Does SQL Server 2005 have something like setup.iss?

Is there a way to capture the steps in a manual installation of SQL Server 2005 into a file similar to setup.iss in 2000? If there is, it's not readily apparent.

I've modified a template.ini file and used it for a successful installation. It's just that it would be more convenient to replay a perfectly executed manual installation. It isn't always obvious which selections in a manual install correspond to specific keywords in template.ini.

No, sorry, this isn't available for SQL Server 2005

Sunday, March 25, 2012

Does sp3a Pretected SQL Server 2000 from Slammer?

We have a SQL Server 2000 with SP1 installation on a Windows 2000 Server PC,
which is connected to the internet. Everytime after the PC is rebooted, in
about 10 to 20 minutes, it starts sending out data packets to random IP addr
esses at a very high rate.
After I installed SP3a, it still does the same except at a much slower rate.
It looks like the PC is infected by the slammer virus. How can I tell for s
ure? If it is slammer virus, why doesn't SP3a fix it completely? Thanks.Make sure you actually have installed the service pack. What do you get if
you run @.@.Version?
Andrew J. Kelly SQL MVP
"Frank" <frankxchen@.yahoo.com> wrote in message
news:363A6A75-D250-401C-A708-8E58604E86C1@.microsoft.com...
> We have a SQL Server 2000 with SP1 installation on a Windows 2000 Server
PC, which is connected to the internet. Everytime after the PC is rebooted,
in about 10 to 20 minutes, it starts sending out data packets to random IP
addresses at a very high rate. After I installed SP3a, it still does the
same except at a much slower rate. It looks like the PC is infected by the
slammer virus. How can I tell for sure? If it is slammer virus, why doesn't
SP3a fix it completely? Thanks.|||SP3a will resolve the problem with Slammer.
You should scan the machine to see what other patches your missing.
http://www.microsoft.com/technet/se...s/mbsahome.mspx
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

Monday, March 19, 2012

Does NEWID() affect my insert performance?

I have a SQL script, which is run during installation, as I want a
particular table to be populated initially. For this particular table I
have around 4000 recs that need to be populated. The script first
deletes all the rows in the table by the following statement:
Delete from [dbo].[Table1]
GO
Then there are 4000 following insert statement is as follows:
INSERT INTO [dbo].[Table1]
(Field1, Field2,Field3,Field4,Field5,Field6,Field7)
VALUES
(NEWID(),'0', '0', 'Test text','User1',GETDATE(),'Test Text')
GO
Since I have started using this script, my installer takes considerably
more time ....I cannot do a bulk insert using CSV because I am using
NEWID().
Is there a workaround?
Thanks.
"Pratham" <pratham17@.gmail.com> wrote in message
news:1144101429.666024.8280@.z34g2000cwc.googlegrou ps.com...
>I have a SQL script, which is run during installation, as I want a
> particular table to be populated initially. For this particular table I
> have around 4000 recs that need to be populated. The script first
> deletes all the rows in the table by the following statement:
> Delete from [dbo].[Table1]
> GO
> Then there are 4000 following insert statement is as follows:
> INSERT INTO [dbo].[Table1]
> (Field1, Field2,Field3,Field4,Field5,Field6,Field7)
> VALUES
> (NEWID(),'0', '0', 'Test text','User1',GETDATE(),'Test Text')
> GO
> Since I have started using this script, my installer takes considerably
> more time ....I cannot do a bulk insert using CSV because I am using
> NEWID().
> Is there a workaround?
>
The problem with using NEWID() like this is that the values are very
unordered, and so the index inserts get scattered all over. SQL Server 2005
introduces NEWSEQUENTIALID() to address this problem.
http://msdn2.microsoft.com/en-us/library/ms189786.aspx
But 4000 isn't a ton of rows in any case, and should take less than 10
seconds either way.
David
|||Thanks David, But I am using SQL 2000. Does anyone know, a way to do
this without changing the schema of the table?
Thanks
|||I agree with David that there should be no noticeable difference using
NEWID() with only 4000 rows. You mentioned that your installer takes
considerably longer but are you certain that it is this script that is the
cause?
Hope this helps.
Dan Guzman
SQL Server MVP
"Pratham" <pratham17@.gmail.com> wrote in message
news:1144101429.666024.8280@.z34g2000cwc.googlegrou ps.com...
>I have a SQL script, which is run during installation, as I want a
> particular table to be populated initially. For this particular table I
> have around 4000 recs that need to be populated. The script first
> deletes all the rows in the table by the following statement:
> Delete from [dbo].[Table1]
> GO
> Then there are 4000 following insert statement is as follows:
> INSERT INTO [dbo].[Table1]
> (Field1, Field2,Field3,Field4,Field5,Field6,Field7)
> VALUES
> (NEWID(),'0', '0', 'Test text','User1',GETDATE(),'Test Text')
> GO
> Since I have started using this script, my installer takes considerably
> more time ....I cannot do a bulk insert using CSV because I am using
> NEWID().
> Is there a workaround?
> Thanks.
>
|||You're change is probably because you are doing single inserts instead of
bulk insert. You might see if doing a truncate instead of delete buys you
enough to get your performance back.
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
"Pratham" <pratham17@.gmail.com> wrote in message
news:1144101429.666024.8280@.z34g2000cwc.googlegrou ps.com...
>I have a SQL script, which is run during installation, as I want a
> particular table to be populated initially. For this particular table I
> have around 4000 recs that need to be populated. The script first
> deletes all the rows in the table by the following statement:
> Delete from [dbo].[Table1]
> GO
> Then there are 4000 following insert statement is as follows:
> INSERT INTO [dbo].[Table1]
> (Field1, Field2,Field3,Field4,Field5,Field6,Field7)
> VALUES
> (NEWID(),'0', '0', 'Test text','User1',GETDATE(),'Test Text')
> GO
> Since I have started using this script, my installer takes considerably
> more time ....I cannot do a bulk insert using CSV because I am using
> NEWID().
> Is there a workaround?
> Thanks.
>

Does NEWID() affect my insert performance?

I have a SQL script, which is run during installation, as I want a
particular table to be populated initially. For this particular table I
have around 4000 recs that need to be populated. The script first
deletes all the rows in the table by the following statement:
Delete from [dbo].[Table1]
GO
Then there are 4000 following insert statement is as follows:
INSERT INTO [dbo].[Table1]
(Field1, Field2,Field3,Field4,Field5,Field6,Field
7)
VALUES
(NEWID(),'0', '0', 'Test text','User1',GETDATE(),'Test Text')
GO
Since I have started using this script, my installer takes considerably
more time ....I cannot do a bulk insert using CSV because I am using
NEWID().
Is there a workaround?
Thanks."Pratham" <pratham17@.gmail.com> wrote in message
news:1144101429.666024.8280@.z34g2000cwc.googlegroups.com...
>I have a SQL script, which is run during installation, as I want a
> particular table to be populated initially. For this particular table I
> have around 4000 recs that need to be populated. The script first
> deletes all the rows in the table by the following statement:
> Delete from [dbo].[Table1]
> GO
> Then there are 4000 following insert statement is as follows:
> INSERT INTO [dbo].[Table1]
> (Field1, Field2,Field3,Field4,Field5,Field6,Field
7)
> VALUES
> (NEWID(),'0', '0', 'Test text','User1',GETDATE(),'Test Text')
> GO
> Since I have started using this script, my installer takes considerably
> more time ....I cannot do a bulk insert using CSV because I am using
> NEWID().
> Is there a workaround?
>
The problem with using NEWID() like this is that the values are very
unordered, and so the index inserts get scattered all over. SQL Server 2005
introduces NEWSEQUENTIALID() to address this problem.
http://msdn2.microsoft.com/en-us/library/ms189786.aspx
But 4000 isn't a ton of rows in any case, and should take less than 10
seconds either way.
David|||Thanks David, But I am using SQL 2000. Does anyone know, a way to do
this without changing the schema of the table?
Thanks|||I agree with David that there should be no noticeable difference using
NEWID() with only 4000 rows. You mentioned that your installer takes
considerably longer but are you certain that it is this script that is the
cause?
Hope this helps.
Dan Guzman
SQL Server MVP
"Pratham" <pratham17@.gmail.com> wrote in message
news:1144101429.666024.8280@.z34g2000cwc.googlegroups.com...
>I have a SQL script, which is run during installation, as I want a
> particular table to be populated initially. For this particular table I
> have around 4000 recs that need to be populated. The script first
> deletes all the rows in the table by the following statement:
> Delete from [dbo].[Table1]
> GO
> Then there are 4000 following insert statement is as follows:
> INSERT INTO [dbo].[Table1]
> (Field1, Field2,Field3,Field4,Field5,Field6,Field
7)
> VALUES
> (NEWID(),'0', '0', 'Test text','User1',GETDATE(),'Test Text')
> GO
> Since I have started using this script, my installer takes considerably
> more time ....I cannot do a bulk insert using CSV because I am using
> NEWID().
> Is there a workaround?
> Thanks.
>|||You're change is probably because you are doing single inserts instead of
bulk insert. You might see if doing a truncate instead of delete buys you
enough to get your performance back.
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
"Pratham" <pratham17@.gmail.com> wrote in message
news:1144101429.666024.8280@.z34g2000cwc.googlegroups.com...
>I have a SQL script, which is run during installation, as I want a
> particular table to be populated initially. For this particular table I
> have around 4000 recs that need to be populated. The script first
> deletes all the rows in the table by the following statement:
> Delete from [dbo].[Table1]
> GO
> Then there are 4000 following insert statement is as follows:
> INSERT INTO [dbo].[Table1]
> (Field1, Field2,Field3,Field4,Field5,Field6,Field
7)
> VALUES
> (NEWID(),'0', '0', 'Test text','User1',GETDATE(),'Test Text')
> GO
> Since I have started using this script, my installer takes considerably
> more time ....I cannot do a bulk insert using CSV because I am using
> NEWID().
> Is there a workaround?
> Thanks.
>

Does NEWID() affect my insert performance?

I have a SQL script, which is run during installation, as I want a
particular table to be populated initially. For this particular table I
have around 4000 recs that need to be populated. The script first
deletes all the rows in the table by the following statement:
Delete from [dbo].[Table1]
GO
Then there are 4000 following insert statement is as follows:
INSERT INTO [dbo].[Table1]
(Field1, Field2,Field3,Field4,Field5,Field6,Field7)
VALUES
(NEWID(),'0', '0', 'Test text','User1',GETDATE(),'Test Text')
GO
Since I have started using this script, my installer takes considerably
more time ....I cannot do a bulk insert using CSV because I am using
NEWID().
Is there a workaround?
Thanks."Pratham" <pratham17@.gmail.com> wrote in message
news:1144101429.666024.8280@.z34g2000cwc.googlegroups.com...
>I have a SQL script, which is run during installation, as I want a
> particular table to be populated initially. For this particular table I
> have around 4000 recs that need to be populated. The script first
> deletes all the rows in the table by the following statement:
> Delete from [dbo].[Table1]
> GO
> Then there are 4000 following insert statement is as follows:
> INSERT INTO [dbo].[Table1]
> (Field1, Field2,Field3,Field4,Field5,Field6,Field7)
> VALUES
> (NEWID(),'0', '0', 'Test text','User1',GETDATE(),'Test Text')
> GO
> Since I have started using this script, my installer takes considerably
> more time ....I cannot do a bulk insert using CSV because I am using
> NEWID().
> Is there a workaround?
>
The problem with using NEWID() like this is that the values are very
unordered, and so the index inserts get scattered all over. SQL Server 2005
introduces NEWSEQUENTIALID() to address this problem.
http://msdn2.microsoft.com/en-us/library/ms189786.aspx
But 4000 isn't a ton of rows in any case, and should take less than 10
seconds either way.
David|||Thanks David, But I am using SQL 2000. Does anyone know, a way to do
this without changing the schema of the table?
Thanks|||I agree with David that there should be no noticeable difference using
NEWID() with only 4000 rows. You mentioned that your installer takes
considerably longer but are you certain that it is this script that is the
cause?
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Pratham" <pratham17@.gmail.com> wrote in message
news:1144101429.666024.8280@.z34g2000cwc.googlegroups.com...
>I have a SQL script, which is run during installation, as I want a
> particular table to be populated initially. For this particular table I
> have around 4000 recs that need to be populated. The script first
> deletes all the rows in the table by the following statement:
> Delete from [dbo].[Table1]
> GO
> Then there are 4000 following insert statement is as follows:
> INSERT INTO [dbo].[Table1]
> (Field1, Field2,Field3,Field4,Field5,Field6,Field7)
> VALUES
> (NEWID(),'0', '0', 'Test text','User1',GETDATE(),'Test Text')
> GO
> Since I have started using this script, my installer takes considerably
> more time ....I cannot do a bulk insert using CSV because I am using
> NEWID().
> Is there a workaround?
> Thanks.
>|||You're change is probably because you are doing single inserts instead of
bulk insert. You might see if doing a truncate instead of delete buys you
enough to get your performance back.
--
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
"Pratham" <pratham17@.gmail.com> wrote in message
news:1144101429.666024.8280@.z34g2000cwc.googlegroups.com...
>I have a SQL script, which is run during installation, as I want a
> particular table to be populated initially. For this particular table I
> have around 4000 recs that need to be populated. The script first
> deletes all the rows in the table by the following statement:
> Delete from [dbo].[Table1]
> GO
> Then there are 4000 following insert statement is as follows:
> INSERT INTO [dbo].[Table1]
> (Field1, Field2,Field3,Field4,Field5,Field6,Field7)
> VALUES
> (NEWID(),'0', '0', 'Test text','User1',GETDATE(),'Test Text')
> GO
> Since I have started using this script, my installer takes considerably
> more time ....I cannot do a bulk insert using CSV because I am using
> NEWID().
> Is there a workaround?
> Thanks.
>

Does MSDE listen on 1433 by default?

Does a default installation of MSDE listen for connections on TCP/IP port
1433 by default or do I need to explicitly turn the TCP/IP listener on using
svrnetcn.exe?
(I'm using W2kR4 (v5.00.2195) and MSDE v8.000.761)
hi,
sparky62 wrote:
> Does a default installation of MSDE listen for connections on TCP/IP
> port 1433 by default or do I need to explicitly turn the TCP/IP
> listener on using svrnetcn.exe?
> (I'm using W2kR4 (v5.00.2195) and MSDE v8.000.761)
if network protocols have been enabled at install time
(DISABLENETWORKPROTOCOLS=0 parameter) TCP/IP port 1433 is assigned by
default to a default instance, where named instances use by default
dynamically assigned port, and thus UDP 1434 is needed to..
The SQL Server Resolution Service, which operates on UDP port 1434, provides
a way for clients to query for the appropriate network endpoints to use for
a particular SQL Server instance... this handshake is provided at connection
time via MDAC stack (MDAC must be at 2.6 level at least) , the SQL Server
Resolution Service queries the SQL Server instance for the port it is
listening to and transfer that info to the client redirecting the dialog to
that port...
if a static port has been assigned, the SQL Server Resolution Service is no
longer needed but you have to define an Alias pointing to the server on the
correct port on each remote client..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

Does MS Access installation is required for running application that uses Access mdb file

Hi,

I am developing an application that uses Access database (mdb file) to store the user data. The user of this application is not interested in the database file (to view in MS Access Environment). Does the user machine requires MS Access installation to run my application or just some couple of dlls (OleDB driver, Access DB Engine,..) should be enough to run my application?

Thanks,

Rao

No, they don't need Access. They will simply need to have MDAC installed, and chances are it will already be there. If not get it here

http://msdn.microsoft.com/data/ref/mdac/

|||

The Information is helpful.

Thanks

Sunday, March 11, 2012

Does In-place upgrade set compatibility level to 9.0

This may be very obvious and when I get to the first test server I will find out, but I only have a new installation of SQL2K5 so far to test with. I have several databases that need to be upgraded to run on 2K5, but the application requires them to run in 8.0 compatibility. Does this mean that an in-place upgrade is not an option?

I apologize if this is a silly question, but I have not yet found the answer specifically.

Thanks very much.

No, it does not change the compatibility level. It leaves it at 8.0.|||

So even on an in-place upgrade you still have to go to each database and manually change the compatibility level? This tells me that it only saves me the transfer or moving of the databases themselves, right?

Thanks!

|||

Saves you moving databases, having to export/import logins from master, jobs from msdb, etc.

But it doesn't assume you want compatibility level 9.0 -and that, in my opinion, is a good thing.

Sunday, February 19, 2012

documentation to install sql 2005 express remotely

Hi all,

I'm just wondering if there is documentation anywhere to help me with installation of SQL 2005 Express on a remote computer. I've set up IIS 6.0 and Windows Server 2003 Web Edition on another computer and am planning to use that for a development server.

Currently I've already installed VWD Express (local computer) and SQL 2005 Express, as well as SQL Query Manager (remote computer). But I seem to be having problems with VWD being able to create databases when i edit the code remotely.

For example when I right-click on "Data Connections" in the "Database Explorer" to create a new database it won't let me. The only way I can do this is to add a connection to a database which I have previously created. And even then there are still problems.

If I set up the database by adding a connection I cannot seem to create stored procedures. The error message I keep getting is "This feature is not supported in Visual Developer".

Is this due to wrong settings whilst installing SQL Express? Or am I just not configuring it right?

Any help on this issue would be greatly appreciated.

Thanks.

I'm not totally up on the capabilities of VWD with regards to database management. There is also the issue of User Instances, which is the default when creating database in VS for many cases. User Instances do not support remote connections, so that would cause problems.

In order to troubleshoot this one, you should simply the scenario by taking VS out of the picture. Use either Managment Studio Express of SQLCmd from your local computer to connect to the remote instance of SQL Express and try to create a database. If that works, try to perfrom some other task against that database. If that works, then the issue is in VS. If you have problems with SSMSE or SQLCmd, then we can look more closely at the SQL issue.

Regards,

Mike Wachal
SQL Express team

-
Check out my tips for getting your answer faster and how to ask a good question: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=307712&SiteID=1

|||

Hi Mike,

As you were saying using Management Studio Express is fine. I can connect to the database remotely and am able to create databases and all that.

The only problem is that I'm currently learning ASP.NET and most of the books utilise VWD Express Edition interface to create, manage and run databases including using the inbuilt (Database Explorer) stored procedures capabilities in VWD. And what they are teaching is to use these locally and not in a remote situation.

I'm just wondering, is there a way to create a stored procedures folder or something similar in SQL Management Express?

I haven't had much experience with MS SQL so please bear with me :)

Thanks for your prompt reply and help.

|||

Stored Procedures are a built-in part of SQL Server, you don't need to create a folder for them. In Management Studio, you should see a folder icon that says Programmability. If you expand that, you will find a place already there for Stored Procedures. When you create a Stored Procedure, they automatically appear in that list, there is no need to specifically put them there.

In order to create a new Stored Procedure in Management Studio you can either right-click on the Stored Procedure "folder" and click the New command, or you can simply open a new query windows against your target database and write a CREATE PROCEDURE script in T-SQL.

Like I mentioned, I think the problem you are facing is related to the default settings of VWD that result in using a User Instance, which only supports a local connection. All of the VS Express products are designed to be used for local development by default. I don't know any specifics about using them to develop against a remote server, other than the fact that you can't use User Instances. As far as I know, there is no way to turn off the default use of User Instances in VS Express products, but you can modify the connection strings manually once they've been created to remove the keyword. This would likely require you to move the database from your local system to the remote server and attach the database there as well.

I would suggest you check out http://forums.asp.net/ to ask more specific question about VWD functionaltiy. I'm out of my element when it comes to web development and VWD.

Regards,

Mike Wachal
SQL Express team

|||

Hi Mike,

Thanks for that. I'll try and post up some questions on the asp.net forums.

documentation to install sql 2005 express remotely

Hi all,

I'm just wondering if there is documentation anywhere to help me with installation of SQL 2005 Express on a remote computer. I've set up IIS 6.0 and Windows Server 2003 Web Edition on another computer and am planning to use that for a development server.

Currently I've already installed VWD Express (local computer) and SQL 2005 Express, as well as SQL Query Manager (remote computer). But I seem to be having problems with VWD being able to create databases when i edit the code remotely.

For example when I right-click on "Data Connections" in the "Database Explorer" to create a new database it won't let me. The only way I can do this is to add a connection to a database which I have previously created. And even then there are still problems.

If I set up the database by adding a connection I cannot seem to create stored procedures. The error message I keep getting is "This feature is not supported in Visual Developer".

Is this due to wrong settings whilst installing SQL Express? Or am I just not configuring it right?

Any help on this issue would be greatly appreciated.

Thanks.

I'm not totally up on the capabilities of VWD with regards to database management. There is also the issue of User Instances, which is the default when creating database in VS for many cases. User Instances do not support remote connections, so that would cause problems.

In order to troubleshoot this one, you should simply the scenario by taking VS out of the picture. Use either Managment Studio Express of SQLCmd from your local computer to connect to the remote instance of SQL Express and try to create a database. If that works, try to perfrom some other task against that database. If that works, then the issue is in VS. If you have problems with SSMSE or SQLCmd, then we can look more closely at the SQL issue.

Regards,

Mike Wachal
SQL Express team

-
Check out my tips for getting your answer faster and how to ask a good question: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=307712&SiteID=1

|||

Hi Mike,

As you were saying using Management Studio Express is fine. I can connect to the database remotely and am able to create databases and all that.

The only problem is that I'm currently learning ASP.NET and most of the books utilise VWD Express Edition interface to create, manage and run databases including using the inbuilt (Database Explorer) stored procedures capabilities in VWD. And what they are teaching is to use these locally and not in a remote situation.

I'm just wondering, is there a way to create a stored procedures folder or something similar in SQL Management Express?

I haven't had much experience with MS SQL so please bear with me :)

Thanks for your prompt reply and help.

|||

Stored Procedures are a built-in part of SQL Server, you don't need to create a folder for them. In Management Studio, you should see a folder icon that says Programmability. If you expand that, you will find a place already there for Stored Procedures. When you create a Stored Procedure, they automatically appear in that list, there is no need to specifically put them there.

In order to create a new Stored Procedure in Management Studio you can either right-click on the Stored Procedure "folder" and click the New command, or you can simply open a new query windows against your target database and write a CREATE PROCEDURE script in T-SQL.

Like I mentioned, I think the problem you are facing is related to the default settings of VWD that result in using a User Instance, which only supports a local connection. All of the VS Express products are designed to be used for local development by default. I don't know any specifics about using them to develop against a remote server, other than the fact that you can't use User Instances. As far as I know, there is no way to turn off the default use of User Instances in VS Express products, but you can modify the connection strings manually once they've been created to remove the keyword. This would likely require you to move the database from your local system to the remote server and attach the database there as well.

I would suggest you check out http://forums.asp.net/ to ask more specific question about VWD functionaltiy. I'm out of my element when it comes to web development and VWD.

Regards,

Mike Wachal
SQL Express team

|||

Hi Mike,

Thanks for that. I'll try and post up some questions on the asp.net forums.