MS SQL Setup for beginners

:) Hi dear fellow members,

I am a newbie to MS SQL. I already completed the installations on the SERVER side and CLIENT side. I have an inventory database in Ms Access that I want to transfer into MS SQL SERVER 2000. Is there anybody who can help me how to do it?

I would be very thankful to anybody who can help like me
who is new to SQL

Regards.

BOBOY PONCEUse the DTS under your tools menu. This will bring in the whole table.
You can create a new table in the server and import the data only.

MS sql server on workgroup not domain.

Hi have a small network setup and have MS sql server on workstation.
Can access it locally but cannot access it from other work stations.
I am assuming it is some sort of logon error, being it is not a
domain. Any ideas on getting by this ?Two possible issues.

One it's installed on Win XP with service pack 2. SP2 has an automatic
firewall that you will need to punch a hole through.

Two the SQL Server is configured for Windows only authentication. Since you
can access it locally you are probably a member of the local administrators
group and as such are granted sa rights by default. Windows only
authentication will not work for remote connections in a work group. You
will need to use SQL Server standard security in mixed mode.

Hope this helps,
Danny

"Father Jack Hackett" <Jachack@.rcc.org> wrote in message
news:j8r4q0djmla88go6hdbraesv6nl4n4d3cd@.4ax.com...
> Hi have a small network setup and have MS sql server on workstation.
> Can access it locally but cannot access it from other work stations.
> I am assuming it is some sort of logon error, being it is not a
> domain. Any ideas on getting by this ?|||I have been trying to set it up on a local workgroup with all XP home
edition computers, I am running into the same problem.

Lionel

On Tue, 23 Nov 2004 12:45:16 GMT, "Danny" <istdrs@.flash.net> wrote:

>Two possible issues.
>One it's installed on Win XP with service pack 2. SP2 has an automatic
>firewall that you will need to punch a hole through.
>Two the SQL Server is configured for Windows only authentication. Since you
>can access it locally you are probably a member of the local administrators
>group and as such are granted sa rights by default. Windows only
>authentication will not work for remote connections in a work group. You
>will need to use SQL Server standard security in mixed mode.
>Hope this helps,
>Danny
>
>"Father Jack Hackett" <Jachack@.rcc.org> wrote in message
>news:j8r4q0djmla88go6hdbraesv6nl4n4d3cd@.4ax.com...
>> Hi have a small network setup and have MS sql server on workstation.
>> Can access it locally but cannot access it from other work stations.
>> I am assuming it is some sort of logon error, being it is not a
>> domain. Any ideas on getting by this ?

MS SQL Server 2005 June CTP Setup Error

Hello,
I'm trying to setup MS SQL Server 2005 June CTP. Everything seemed to be
fine except Reporting Services failed to install, blow is the Setup Log with
the section that has the relavent failure:
CreateAspApp: start time: 11:44:01
CreateAspApp: CustomActionData: /LM/W3SVC/1/Root/Reports
CreateAspApp: Error 0x8004e00f: failed to create web application:
/LM/W3SVC/1/Root/Reports
MSI (s) (38!B0) [11:44:12:625]: Product: Microsoft SQL Server 2005 Reporting
Services CTP -- Error 25619. The setup failed to create web application:
/LM/W3SVC/1/Root/Reports. The error code is -2147164145.
Error 25619. The setup failed to create web application:
/LM/W3SVC/1/Root/Reports. The error code is -2147164145.
CreateAspApp: end time: 11:44:12, elapsed: 38475601.000000 (seconds)
Can someone shed some light on this?
--
GeorgeWorked fine for me.
--
Thanks,
ID
"George P boutwell" wrote:
> Hello,
> I'm trying to setup MS SQL Server 2005 June CTP. Everything seemed to be
> fine except Reporting Services failed to install, blow is the Setup Log with
> the section that has the relavent failure:
> CreateAspApp: start time: 11:44:01
> CreateAspApp: CustomActionData: /LM/W3SVC/1/Root/Reports
> CreateAspApp: Error 0x8004e00f: failed to create web application:
> /LM/W3SVC/1/Root/Reports
> MSI (s) (38!B0) [11:44:12:625]: Product: Microsoft SQL Server 2005 Reporting
> Services CTP -- Error 25619. The setup failed to create web application:
> /LM/W3SVC/1/Root/Reports. The error code is -2147164145.
> Error 25619. The setup failed to create web application:
> /LM/W3SVC/1/Root/Reports. The error code is -2147164145.
> CreateAspApp: end time: 11:44:12, elapsed: 38475601.000000 (seconds)
> Can someone shed some light on this?
> --
> George|||Great! Now if only I could get it to work for me, I could get back to real
coding and getting some real work done...
I did some digging there isn't really and 2005 documentation that covers
this problem, there is some SQL 2000 that says to ensure the
IWAM_computername user isn't disabled and the DTC (Distributed Transaction
Coordinator) service is running. That could be my problem DTC is not
running, however, when I try to run it it gives me an error:
The Distributed Transaction Coordinator service terminated with
service-specific error 3221229584 (0xC0001010).
So I'm back to still not able to do it. :(
--
George
"exkievan" wrote:
> Worked fine for me.
> --
> Thanks,
> ID
>
> "George P boutwell" wrote:
> > Hello,
> >
> > I'm trying to setup MS SQL Server 2005 June CTP. Everything seemed to be
> > fine except Reporting Services failed to install, blow is the Setup Log with
> > the section that has the relavent failure:
> >
> > CreateAspApp: start time: 11:44:01
> > CreateAspApp: CustomActionData: /LM/W3SVC/1/Root/Reports
> > CreateAspApp: Error 0x8004e00f: failed to create web application:
> > /LM/W3SVC/1/Root/Reports
> > MSI (s) (38!B0) [11:44:12:625]: Product: Microsoft SQL Server 2005 Reporting
> > Services CTP -- Error 25619. The setup failed to create web application:
> > /LM/W3SVC/1/Root/Reports. The error code is -2147164145.
> >
> > Error 25619. The setup failed to create web application:
> > /LM/W3SVC/1/Root/Reports. The error code is -2147164145.
> > CreateAspApp: end time: 11:44:12, elapsed: 38475601.000000 (seconds)
> >
> > Can someone shed some light on this?
> >
> > --
> > George|||On Wed, 22 Jun 2005 06:31:08 -0700, George P Boutwell wrote:
> Great! Now if only I could get it to work for me, I could get back to real
> coding and getting some real work done...
> I did some digging there isn't really and 2005 documentation that covers
> this problem, there is some SQL 2000 that says to ensure the
> IWAM_computername user isn't disabled and the DTC (Distributed Transaction
> Coordinator) service is running. That could be my problem DTC is not
> running, however, when I try to run it it gives me an error:
> The Distributed Transaction Coordinator service terminated with
> service-specific error 3221229584 (0xC0001010).
> So I'm back to still not able to do it. :(
I tried several searches on KnowledgeBase and come-up empty, till I tried
an search on service-specified error 3221229584, which produced the
following:
http://news.gmane.org/gmane.linux.colinux.devel/cutoff=2420
this seemed to have fixed my DTC service, it now runs as expected. And
after uninstalling, rebooting, and re-installing SQL Server 2005 June CTP,
I now have the Report Services working.
Georgesql

MS SQL Server 2005 - SQL Agent problems

I am currently running SQL Server 2005 on a stand alone (not a domain
member) Windows Server 2003, this server was installed during setup
using local user accounts as service accounts.
As far as I recall at the time everything, including the SQL agent
functioned normally. At this time, the server itself still seems to
be running fine, however the SQL Agent service will not start.
I can not be sure as up until recently we haven't really been using
the SQL Agent, however I believe the problem would have started around
the time that service pack 1 was installed.
The following is the event log error message that is generated
everytime the SQL Agent service attempts to start:
###
Event Type: Error
Event Source: SQLSERVERAGENT
Event Category: Service Control
Event ID: 103
Date: 7/24/2007
Time: 3:55:22 PM
User: N/A
Computer: DBSERVER
Description:
SQLServerAgent could not be started (reason: SQLServerAgent must be
able to connect to SQLServer as SysAdmin, but '(Unknown)' is not a
member of the SysAdmin role).
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
###
Please note that where the error message should indicate the name of
the service account (svc_sqlagent) it instead indicates "Unknown".
Also that SQL Server database engine running under the its own local
user service account (svc_sqlserver) works fine.
I have since tried recreating and reassigning a new local user service
account for the SQL Agent using two methods,
the first, the official approved method using the SQL Server
Configuration Manager:
results in the simple and vague error dialog box:
Title bar: WMI Provider Error
Error message: The process terminated unexpectedly. [0x8007042b]
The above error however produces no entries in any of the event logs.
If I start with a plain vanilla local user account, the config manager
does manage to setup some but not all of the special permissions/group
memberships necessary for the account to operate, before the error
occurs, but it does not appear to be consistent in how far it gets in
applying the correct parameters to the account.
the second method I used, was the manual service account setup from
knowledge base article Q283811.
this allows me to get the account setup, and the service set to log in
as the account, but when the service attempts to start, it fails, with
the same event log entry shown above.
also while trying to resolve all this SP2 became available, I first
tried to resolve this issue before installing SP2 however when I was
unable to, I went ahead and applied SP2 in the hopes that it might
help, as near as I can tell it has no effect, I attempted all the
previous methods and got the same results.
Any help with this would be greatly appreciated.
Thank you,
Jeffrey WilliamsDid you verify that the local account that you want to use for running SQL
Agent service is a member of the Local Users & Groups in the Group
'Administrators'?
and that the SQL Server login has the server role of 'sysadmin'
If the local user has that security it should be able to run SQL Agent
~Ellen
--
Thank you for sharing your knowledge
"sailorfej" wrote:
> I am currently running SQL Server 2005 on a stand alone (not a domain
> member) Windows Server 2003, this server was installed during setup
> using local user accounts as service accounts.
> As far as I recall at the time everything, including the SQL agent
> functioned normally. At this time, the server itself still seems to
> be running fine, however the SQL Agent service will not start.
> I can not be sure as up until recently we haven't really been using
> the SQL Agent, however I believe the problem would have started around
> the time that service pack 1 was installed.
> The following is the event log error message that is generated
> everytime the SQL Agent service attempts to start:
> ###
> Event Type: Error
> Event Source: SQLSERVERAGENT
> Event Category: Service Control
> Event ID: 103
> Date: 7/24/2007
> Time: 3:55:22 PM
> User: N/A
> Computer: DBSERVER
> Description:
> SQLServerAgent could not be started (reason: SQLServerAgent must be
> able to connect to SQLServer as SysAdmin, but '(Unknown)' is not a
> member of the SysAdmin role).
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> ###
> Please note that where the error message should indicate the name of
> the service account (svc_sqlagent) it instead indicates "Unknown".
> Also that SQL Server database engine running under the its own local
> user service account (svc_sqlserver) works fine.
> I have since tried recreating and reassigning a new local user service
> account for the SQL Agent using two methods,
> the first, the official approved method using the SQL Server
> Configuration Manager:
> results in the simple and vague error dialog box:
> Title bar: WMI Provider Error
> Error message: The process terminated unexpectedly. [0x8007042b]
> The above error however produces no entries in any of the event logs.
> If I start with a plain vanilla local user account, the config manager
> does manage to setup some but not all of the special permissions/group
> memberships necessary for the account to operate, before the error
> occurs, but it does not appear to be consistent in how far it gets in
> applying the correct parameters to the account.
> the second method I used, was the manual service account setup from
> knowledge base article Q283811.
> this allows me to get the account setup, and the service set to log in
> as the account, but when the service attempts to start, it fails, with
> the same event log entry shown above.
> also while trying to resolve all this SP2 became available, I first
> tried to resolve this issue before installing SP2 however when I was
> unable to, I went ahead and applied SP2 in the hopes that it might
> help, as near as I can tell it has no effect, I attempted all the
> previous methods and got the same results.
> Any help with this would be greatly appreciated.
> Thank you,
> Jeffrey Williams
>|||On Aug 15, 2:56 pm, Ellen <DBAEl...@.community.nospam> wrote:
> Did you verify that the local account that you want to use for running SQL
> Agent service is a member of the Local Users & Groups in the Group
> 'Administrators'?
> and that the SQL Server login has the server role of 'sysadmin'
> If the local user has that security it should be able to run SQL Agent
> ~Ellen
> --
> Thank you for sharing your knowledge
> "sailorfej" wrote:
> > I am currently running SQL Server 2005 on a stand alone (not a domain
> > member) Windows Server 2003, this server was installed during setup
> > using local user accounts as service accounts.
> > As far as I recall at the time everything, including the SQL agent
> > functioned normally. At this time, the server itself still seems to
> > be running fine, however the SQL Agent service will not start.
> > I can not be sure as up until recently we haven't really been using
> > the SQL Agent, however I believe the problem would have started around
> > the time that service pack 1 was installed.
> > The following is the event log error message that is generated
> > everytime the SQL Agent service attempts to start:
> > ###
> > Event Type: Error
> > Event Source: SQLSERVERAGENT
> > Event Category: Service Control
> > Event ID: 103
> > Date: 7/24/2007
> > Time: 3:55:22 PM
> > User: N/A
> > Computer: DBSERVER
> > Description:
> > SQLServerAgent could not be started (reason: SQLServerAgent must be
> > able to connect to SQLServer as SysAdmin, but '(Unknown)' is not a
> > member of the SysAdmin role).
> > For more information, see Help and Support Center at
> >http://go.microsoft.com/fwlink/events.asp.
> > ###
> > Please note that where the error message should indicate the name of
> > the service account (svc_sqlagent) it instead indicates "Unknown".
> > Also that SQL Server database engine running under the its own local
> > user service account (svc_sqlserver) works fine.
> > I have since tried recreating and reassigning a new local user service
> > account for the SQL Agent using two methods,
> > the first, the official approved method using the SQL Server
> > Configuration Manager:
> > results in the simple and vague error dialog box:
> > Title bar: WMI Provider Error
> > Error message: The process terminated unexpectedly. [0x8007042b]
> > The above error however produces no entries in any of the event logs.
> > If I start with a plain vanilla local user account, the config manager
> > does manage to setup some but not all of the special permissions/group
> > memberships necessary for the account to operate, before the error
> > occurs, but it does not appear to be consistent in how far it gets in
> > applying the correct parameters to the account.
> > the second method I used, was the manual service account setup from
> > knowledge base article Q283811.
> > this allows me to get the account setup, and the service set to log in
> > as the account, but when the service attempts to start, it fails, with
> > the same event log entry shown above.
> > also while trying to resolve all this SP2 became available, I first
> > tried to resolve this issue before installing SP2 however when I was
> > unable to, I went ahead and applied SP2 in the hopes that it might
> > help, as near as I can tell it has no effect, I attempted all the
> > previous methods and got the same results.
> > Any help with this would be greatly appreciated.
> > Thank you,
> > Jeffrey Williams
Hi Ellen,
Yes, I did. As I described in my previous message, both methods I
used in setting up the service account resulted in the correct
permissions for the account, in addition, the original account setup
carried out during the SQL Servers installation setup the service
account with the correct permissions, and the service didn't start to
have problems until later.
I believe the there is some break in the interface between the WMI/NT
Auth components, and the SQL Server Auth mechanism, this is why I made
sure to include the info for the WMI error dialog, and pointed that in
the event log error message the service account is not correctly
identified, but is instead listed as "unknown". If this were a
standard permissions issue, the account would have been correctly
identified as "svc_sqlagent".
If you have any other ideas, I would very much appreciate hearing
them.
Thanks,
Jeff

MS SQL Question regarding page/index defrag.

I know the shortcut to 'defragging' the database to eliminate andreclaim 'whitespace' in data and index pages is to setup a maintenanceplan. This doesn't work for me for two reasons:1. I like to know how things work.2. I can not create maintenance plans with my hosted provider.I use the following T-SQL to rebuild all indexes on all tables:-- exec sp_MSforeachtable "DBCC DBREINDEX ('?', ' ', 90)But, does that not only address indexes? What about getting whitepaceback from data in tables themselves?Am I over-thinking this?When you're paying for SQL by the MB and generate a lot of data (with afair amount of churn) you want to keep it optimized and efficient,right?You could run DBCC ShrinkDB, DBCC ShrinkFile and Truncat your transaction Log, I think all of the above will not return all of the space for you because there is some space SQL Server marks as Active. BTW Maintaince plans are Server based while Jobs can run your DBCCs for your database only. Hope this helps.