Create a new SQL Server database

I have Visual Studio 2003 Developer edition installed. The "Create a new SQL Server database" item is not enabled in the server explorer when I right click on connection. Do I have to instal a different version...or is there a common solution for this?

Thank you.

CJG

in VS 2003 , you can't .

to create a new database for SqlServer , you have to use Enterprise Manager for your SQL server version ,

if you dont have one , you can install it fromhere:

Create a new maintenance plan

I have installed SQLServer 2005 from Small Business Server premium edition. The package has been upgraded to SP2 and all the fixes have been applied.

I want to create a new maintenance plan to automate my DB backup procedures using SQL Server Management Studio. I start Management Studio and right click on the management folder and I I see is "Refresh" there is no "Create New Maintenance" plan presented.

I have tried this using the sa built-in account and the server administrator account both of which have sysadmin priviledges. I have also tried it from a client machine with another sysadmin userid but they all give the same results.

I checked to see if SSIS was installed. The add/remove programs wizard for SQL Server shows Integration Services SP2 is installed but I went ahead anyway and re-installed without error.

It seems that either SSIS is not running or I my user roles are preventing the maintenance wizard from running. Is there some way that I can tell if, in fact, SSIS is properly installed and running?

Thanks.

To create or manage maintenance plans, you must be a member of the sysadmin fixed server role. Note that Object Explorer only displays maintenance plans if the user is a member of the sysadmin fixed server role.

See http://technet.microsoft.com/en-us/library/ms189036(SQL.90).aspxsql

Create a new maintenance plan

I have installed SQLServer 2005 from Small Business Server premium edition. The package has been upgraded to SP2 and all the fixes have been applied.

I want to create a new maintenance plan to automate my DB backup procedures using SQL Server Management Studio. I start Management Studio and right click on the management folder and I I see is "Refresh" there is no "Create New Maintenance" plan presented.

I have tried this using the sa built-in account and the server administrator account both of which have sysadmin priviledges. I have also tried it from a client machine with another sysadmin userid but they all give the same results.

I checked to see if SSIS was installed. The add/remove programs wizard for SQL Server shows Integration Services SP2 is installed but I went ahead anyway and re-installed without error.

It seems that either SSIS is not running or I my user roles are preventing the maintenance wizard from running. Is there some way that I can tell if, in fact, SSIS is properly installed and running?

Thanks.

To create or manage maintenance plans, you must be a member of the sysadmin fixed server role. Note that Object Explorer only displays maintenance plans if the user is a member of the sysadmin fixed server role.

See http://technet.microsoft.com/en-us/library/ms189036(SQL.90).aspx

Crashed C drive, but DB on D drive

SQL 7.0
The C drive crashed, but the DB was safe(?) on drive D.
When a new drive C is installed is there any way to
retore or whatever the database?
Thanks,
DonDon wrote:

> SQL 7.0
> The C drive crashed, but the DB was safe(?) on drive D.
> When a new drive C is installed is there any way to
> retore or whatever the database?
You should be able to attach the databases after you install SQL.
Typically in this scenario if you were using SQL Logins and you don't
have them anymore, you probably lost the passwords. There are ways to
restore the master database which stores these passwords, however I have
never had much success with such a thing and is usually not necessary.
Attaching a database can be done through Enterprise Manager by right
clicking on the databases folder.
Aaron Weiker
http://blogs.sqladvice.com/aweiker
http://aaronweiker.com/|||Hi,
Step -1
Can you tell the location of system databases (Master,model,msdb,tempdb) MDF
and LDF locations. If it is in D drive you can easily make the
SQL server up with all the configurations and data same as old.
1. Install SQL server with same directory structure as old
2. Apply the service pack as old
3. Stop sql server
4. Copy all the MDF and LDF files to the same directory stucture as before
(Ensure that u keep the original some where safe)
5. Start SQL Server
Normally this will enable to have all the databases and Logins same as old.
Step 2
Incase if your system MDF and LDF were lost then, (the below steps will work
if you have MASTER database backup (master.bak))
1. Install SQL server with same directory structure as old
2. Apply service packs
3. Start SQL server in sigle user mode (-m)
4. Restore the master database
5. Restore MSDB database
6. Stop SQL server and copy the MDF and LDF to the directories as old
7. Start SQL server
Step 3
Incase if you dont have the MASTER database backup. Now all depends on luck.
SOme times your ATTACH may not work since you have not
detached the database using SP_DETACH_DB. If attach gives you issue then
probably you have restore the databases from Backup you have
and then create the logins manually and assign permissions.
Thanks
Hari
MCDBA
"Don" <anonymous@.discussions.microsoft.com> wrote in message
news:9d1701c4063f$47542660$a001280a@.phx.gbl...
> SQL 7.0
> The C drive crashed, but the DB was safe(?) on drive D.
> When a new drive C is installed is there any way to
> retore or whatever the database?
> Thanks,
> Don
>

CPU Time

I have a SQL server 2000 standard version installed on a window 2000 server.
It has been working well. Recently, SQL server process sqlservr.exe consume
50%-99% of the CPU time even I didn't issue any SQL server related
operation. There is not any backup or maintain job was set up in the server.
The memory usage doesn't change. I once waited for more than one hour to
complete the process, however it didn't.
Did anyone know what's happened? My computer become really slow and hardly
do anything.
Thanks
YingHi
Is SQL Server 2000 Service Pack 3 or 4 applied. If not, it sounds like the
Slammer Virus that came out 3 years ago.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Ying" <Ying@.discussions.microsoft.com> wrote in message
news:D712A471-053F-448E-A8CA-4A85CCB1EB1C@.microsoft.com...
>I have a SQL server 2000 standard version installed on a window 2000
>server.
> It has been working well. Recently, SQL server process sqlservr.exe
> consume
> 50%-99% of the CPU time even I didn't issue any SQL server related
> operation. There is not any backup or maintain job was set up in the
> server.
> The memory usage doesn't change. I once waited for more than one hour to
> complete the process, however it didn't.
> Did anyone know what's happened? My computer become really slow and hardly
> do anything.
> Thanks
> Ying

CPU Time

I have a SQL server 2000 standard version installed on a window 2000 server.
It has been working well. Recently, SQL server process sqlservr.exe consume
50%-99% of the CPU time even I didn't issue any SQL server related
operation. There is not any backup or maintain job was set up in the server.
The memory usage doesn't change. I once waited for more than one hour to
complete the process, however it didn't.
Did anyone know what's happened? My computer become really slow and hardly
do anything.
Thanks
Ying
Hi
Is SQL Server 2000 Service Pack 3 or 4 applied. If not, it sounds like the
Slammer Virus that came out 3 years ago.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Ying" <Ying@.discussions.microsoft.com> wrote in message
news:D712A471-053F-448E-A8CA-4A85CCB1EB1C@.microsoft.com...
>I have a SQL server 2000 standard version installed on a window 2000
>server.
> It has been working well. Recently, SQL server process sqlservr.exe
> consume
> 50%-99% of the CPU time even I didn't issue any SQL server related
> operation. There is not any backup or maintain job was set up in the
> server.
> The memory usage doesn't change. I once waited for more than one hour to
> complete the process, however it didn't.
> Did anyone know what's happened? My computer become really slow and hardly
> do anything.
> Thanks
> Ying

CPU Time

I have a SQL server 2000 standard version installed on a window 2000 server.
It has been working well. Recently, SQL server process sqlservr.exe consume
50%-99% of the CPU time even I didn't issue any SQL server related
operation. There is not any backup or maintain job was set up in the server.
The memory usage doesn't change. I once waited for more than one hour to
complete the process, however it didn't.
Did anyone know what's happened? My computer become really slow and hardly
do anything.
Thanks
YingHi
Is SQL Server 2000 Service Pack 3 or 4 applied. If not, it sounds like the
Slammer Virus that came out 3 years ago.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Ying" <Ying@.discussions.microsoft.com> wrote in message
news:D712A471-053F-448E-A8CA-4A85CCB1EB1C@.microsoft.com...
>I have a SQL server 2000 standard version installed on a window 2000
>server.
> It has been working well. Recently, SQL server process sqlservr.exe
> consume
> 50%-99% of the CPU time even I didn't issue any SQL server related
> operation. There is not any backup or maintain job was set up in the
> server.
> The memory usage doesn't change. I once waited for more than one hour to
> complete the process, however it didn't.
> Did anyone know what's happened? My computer become really slow and hardly
> do anything.
> Thanks
> Ying

CPU licensing question

We moved from a 4 CPU server to a 2 CPU server and when we installed SQL
Server (Enterprise Edition) on the replacement server we specified 4 CPU
licenses without thinking. We would now like to apply the 2 "spare" CPU
licenses to a new server. Can we just go ahead and apply them (since they're
not useable on the current 2 CPU server) or do we need to somehow remove them
from the 2 CPU server first?
You can specify the number of CPU licenses you have from the SQL Server
license utility in Control Panel. It's a good idea to change it to the
appropriate number just to make life easier from an audit and license
management perspective.
joe.
"J Jetson" <JJetson@.discussions.microsoft.com> wrote in message
news:FE011F53-2309-4ACD-B79D-D906EAC73171@.microsoft.com...
> We moved from a 4 CPU server to a 2 CPU server and when we installed SQL
> Server (Enterprise Edition) on the replacement server we specified 4 CPU
> licenses without thinking. We would now like to apply the 2 "spare" CPU
> licenses to a new server. Can we just go ahead and apply them (since
they're
> not useable on the current 2 CPU server) or do we need to somehow remove
them
> from the 2 CPU server first?

CPU licensing question

We moved from a 4 CPU server to a 2 CPU server and when we installed SQL
Server (Enterprise Edition) on the replacement server we specified 4 CPU
licenses without thinking. We would now like to apply the 2 "spare" CPU
licenses to a new server. Can we just go ahead and apply them (since they're
not useable on the current 2 CPU server) or do we need to somehow remove the
m
from the 2 CPU server first?You can specify the number of CPU licenses you have from the SQL Server
license utility in Control Panel. It's a good idea to change it to the
appropriate number just to make life easier from an audit and license
management perspective.
joe.
"J Jetson" <JJetson@.discussions.microsoft.com> wrote in message
news:FE011F53-2309-4ACD-B79D-D906EAC73171@.microsoft.com...
> We moved from a 4 CPU server to a 2 CPU server and when we installed SQL
> Server (Enterprise Edition) on the replacement server we specified 4 CPU
> licenses without thinking. We would now like to apply the 2 "spare" CPU
> licenses to a new server. Can we just go ahead and apply them (since
they're
> not useable on the current 2 CPU server) or do we need to somehow remove
them
> from the 2 CPU server first?

CPU licensing question

We moved from a 4 CPU server to a 2 CPU server and when we installed SQL
Server (Enterprise Edition) on the replacement server we specified 4 CPU
licenses without thinking. We would now like to apply the 2 "spare" CPU
licenses to a new server. Can we just go ahead and apply them (since they're
not useable on the current 2 CPU server) or do we need to somehow remove them
from the 2 CPU server first?You can specify the number of CPU licenses you have from the SQL Server
license utility in Control Panel. It's a good idea to change it to the
appropriate number just to make life easier from an audit and license
management perspective.
joe.
"J Jetson" <JJetson@.discussions.microsoft.com> wrote in message
news:FE011F53-2309-4ACD-B79D-D906EAC73171@.microsoft.com...
> We moved from a 4 CPU server to a 2 CPU server and when we installed SQL
> Server (Enterprise Edition) on the replacement server we specified 4 CPU
> licenses without thinking. We would now like to apply the 2 "spare" CPU
> licenses to a new server. Can we just go ahead and apply them (since
they're
> not useable on the current 2 CPU server) or do we need to somehow remove
them
> from the 2 CPU server first?