Lowering priority: standard

Showing posts with label standard. Show all posts

Wednesday, March 28, 2012

Maintenance plan error in SQL Server 2000(SP3) Standard Ed!

Hi,
I have delete the user BUILTIN\Administrators, afte that
Maintenance Plan jobs are failed with the following error:
Microsoft (R) SQLMaint Utility (Unicode), Version
[Microsoft SQL-DMO (ODBC SQLState: 28000)] Error 18456:
[Microsoft][ODBC SQL Server Driver][SQL Server]Login
failed for user 'NT AUTHORITY\SYSTEM'.
I have given access to the User, under which SQL Server
Agent services runs.
When i added back the user BUILTIN\Administrators, after
that it's runing fine. Please suggest for above problem.
I appreciate it.
Thanks
ssWhat account was the job set up under? And with which account is the
sqlagent running?
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.

Maintenance Plan Error

Windows 20003 Enterprise server

SQL 2005 Standard with SP2

When I try and create a maintenance plan either via the wizard or just create new, I get the following error. Can anyone help please. thanks

===================================

Cannot show requested dialog.

===================================

Unable to execute requested command.

Program Location:

at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ToolsMenuItem.OnCreateAndShowForm(IServiceProvider sp, XmlDocument doc)
at Microsoft.SqlServer.Management.SqlMgmt.RunningFormsTable.RunningFormsTableImpl.ThreadStarter.StartThread()

===================================

Method not found: 'Void Microsoft.SqlServer.Management.DatabaseMaintenance.TaskUIUtils..ctor()'. (Microsoft.SqlServer.Management.MaintenancePlanWizard)

Program Location:

at Microsoft.SqlServer.Management.MaintenancePlanWizard.MaintenancePlanWizardForm..ctor(XmlDocument doc, IServiceProvider serviceProvider)

Hello Theon,

This sounds like your client tools are older than SP2. The SP2 version of the Microsoft.SqlServer.MaintenancePlanTasks.dll assembly removed the function mentioned in the error message, so that's why the function cannot be found.. Can you check what version of Management Studio you're running, and see if its older than SP2? Also are you running Management Studio on the sql server machine, or connecting to it remotely?

James

|||

Here is the version

Microsoft SQL Server Management Studio 9.00.1399.00
Microsoft Analysis Services Client Tools 2005.090.1399.00
Microsoft Data Access Components (MDAC) 2000.086.3959.00 (srv03_sp2_rtm.070216-1710)
Microsoft MSXML 2.6 3.0 4.0 6.0
Microsoft Internet Explorer 7.0.5730.11
Microsoft .NET Framework 2.0.50727.42
Operating System 5.2.3790

I am connecting on the server

|||Applied sp2 and all is well thanks
|||

Glad to help, Theon.

James

Maintenance Plan Configuration

Hi,
I've just started using SQL Server 2005 Standard and I'm moving database
across from SQL Server 2000.
I have setup a maintenance plan to backup my databases in the new
maintenance plan tool / SSIS but I cannot find any option to delete old
database backup files like I have in SQL Server 2000.
I found the Clean-up History task, but this does not appear to be related to
deleting database backup files.
Can someone please point me in the right direction for configuring this
option so I do not need to write my own job to delete old backup files.John
add a "Maintenance Clean Up" task to your Maintenance plan. This will
give you the option to delete old backfiles or logfiles.
Markus

Maintenance Plan Configuration

Hi,
I've just started using SQL Server 2005 Standard and I'm moving database
across from SQL Server 2000.
I have setup a maintenance plan to backup my databases in the new
maintenance plan tool / SSIS but I cannot find any option to delete old
database backup files like I have in SQL Server 2000.
I found the Clean-up History task, but this does not appear to be related to
deleting database backup files.
Can someone please point me in the right direction for configuring this
option so I do not need to write my own job to delete old backup files.
John
add a "Maintenance Clean Up" task to your Maintenance plan. This will
give you the option to delete old backfiles or logfiles.
Markus

Maintenance Plan Configuration

Friday, March 23, 2012

Maintenance Cleanup Task……

SQL Server 2005 Standard Edition

Windows Server 2003.

I have created an ‘Backup Database Task’ to create the database backups and checked the option “Create a subdirectory for each database”.

When I add the “Maintenance Cleanup Task” I am not getting the similar option to clean the backup files in the subdirectory.

Any suggestion on how to solve this?

I can always uncheck the “Create a subdirectory for each database” option to create the backup files in one location.

Thank you,

Smith

Smith,
Once you create a Sub directory the backup files will be placed there...now in the clean up task there is an option called "Search folder and delete files based on an extension" you need to specify the sub directory folder in the above mentioned option........the clean up task will delete it and also you need to psecify the extension as "bak" to delete backup files.........refer the below link,
http://www.sql-server-performance.com/articles/dba/creating_backup_jobs_p2.aspx

|||

This article could be helpful for you

http://msdn2.microsoft.com/en-us/library/ms345177.aspx

|||

Deepak,

This link says...

"To delete the first-level subfolders, you must explicitly elect to do this by checking the Include first-level subfolders option in the Maintenance Cleanup Task dialog box."

I am not finding the "Includefirst-level subfolders" option to check.

How to check this option.

Thank you

-Smith

|||

Hi,

What Service Pack are you on? You should be getting that option when you Edit the Maintenance Plab Sub-task "Clean up Maintenance Task"

|||

select @.@.version

Thanks,

|||Try to install SQL 2005 SP2 critical update from
http://www.microsoft.com/downloads/details.aspx?FamilyId=e2c358a1-ecc4-4c49-8f65-daa6b7800eec&displaylang=en

refer the below link,
http://support.microsoft.com/kb/933508 as there were many problems relating to maintenance plan which were fixed with critical update ! ! !
|||

Thank you for your suggestions in resolving this issue.

Since it is not a critical issue affecting the production I will wait for the SP3 :-)

Infact when I installed the SP2 I did download the latest copy available.

Thank you,

|||Well i don't think SP3 would be released for sql 2005 as sql 2008 is going to be released in Feb 2008 Smile

Maintenance Cleanup Task……

SQL Server 2005 Standard Edition

Windows Server 2003.

I have created an ‘Backup Database Task’ to create the database backups and checked the option “Create a subdirectory for each database”.

When I add the “Maintenance Cleanup Task” I am not getting the similar option to clean the backup files in the subdirectory.

Any suggestion on how to solve this?

I can always uncheck the “Create a subdirectory for each database” option to create the backup files in one location.

Thank you,

Smith

|||

This article could be helpful for you

http://msdn2.microsoft.com/en-us/library/ms345177.aspx

|||

Deepak,

This link says...

"To delete the first-level subfolders, you must explicitly elect to do this by checking the Include first-level subfolders option in the Maintenance Cleanup Task dialog box."

I am not finding the "Includefirst-level subfolders" option to check.

How to check this option.

Thank you

-Smith

|||

Hi,

What Service Pack are you on? You should be getting that option when you Edit the Maintenance Plab Sub-task "Clean up Maintenance Task"

|||

select @.@.version

Thanks,

Thank you for your suggestions in resolving this issue.

Since it is not a critical issue affecting the production I will wait for the SP3 :-)

Infact when I installed the SP2 I did download the latest copy available.

Thank you,

|||Well i don't think SP3 would be released for sql 2005 as sql 2008 is going to be released in Feb 2008 Smile

Maintenance Cleanup Task……

SQL Server 2005 Standard Edition

Windows Server 2003.

I have created an ‘Backup Database Task’ to create the database backups and checked the option “Create a subdirectory for each database”.

When I add the “Maintenance Cleanup Task” I am not getting the similar option to clean the backup files in the subdirectory.

Any suggestion on how to solve this?

I can always uncheck the “Create a subdirectory for each database” option to create the backup files in one location.

Thank you,

Smith

|||

This article could be helpful for you

http://msdn2.microsoft.com/en-us/library/ms345177.aspx

|||

Deepak,

This link says...

"To delete the first-level subfolders, you must explicitly elect to do this by checking the Include first-level subfolders option in the Maintenance Cleanup Task dialog box."

I am not finding the "Includefirst-level subfolders" option to check.

How to check this option.

Thank you

-Smith

|||

Hi,

What Service Pack are you on? You should be getting that option when you Edit the Maintenance Plab Sub-task "Clean up Maintenance Task"

|||

select @.@.version

Thanks,

Thank you for your suggestions in resolving this issue.

Since it is not a critical issue affecting the production I will wait for the SP3 :-)

Infact when I installed the SP2 I did download the latest copy available.

Thank you,

|||Well i don't think SP3 would be released for sql 2005 as sql 2008 is going to be released in Feb 2008 Smile

sql

Maintenance Cleanup Task……

SQL Server 2005 Standard Edition

Windows Server 2003.

I have created an ‘Backup Database Task’ to create the database backups and checked the option “Create a subdirectory for each database”.

When I add the “Maintenance Cleanup Task” I am not getting the similar option to clean the backup files in the subdirectory.

Any suggestion on how to solve this?

I can always uncheck the “Create a subdirectory for each database” option to create the backup files in one location.

Thank you,

Smith

|||

This article could be helpful for you

http://msdn2.microsoft.com/en-us/library/ms345177.aspx

|||

Deepak,

This link says...

"To delete the first-level subfolders, you must explicitly elect to do this by checking the Include first-level subfolders option in the Maintenance Cleanup Task dialog box."

I am not finding the "Includefirst-level subfolders" option to check.

How to check this option.

Thank you

-Smith

|||

Hi,

What Service Pack are you on? You should be getting that option when you Edit the Maintenance Plab Sub-task "Clean up Maintenance Task"

|||

select @.@.version

Thanks,

Thank you for your suggestions in resolving this issue.

Since it is not a critical issue affecting the production I will wait for the SP3 :-)

Infact when I installed the SP2 I did download the latest copy available.

Thank you,

|||Well i don't think SP3 would be released for sql 2005 as sql 2008 is going to be released in Feb 2008 Smile

Monday, March 19, 2012

Maintaintance plan error

I have sql server 2005 standard edition with service pack 2(9.0.3050),when i
am creating new maintainance plan ,at the end when i click finish button of
the wizard,message i am getting is "one or more arguments are invalid",please
reply me what is the problem asap.
Thanks
Rupesh
It looks like some other people have been experiencing this problem. One
thing that has been suggested in another thread is to assure that you have
SP2 also of Management Studio.
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1823734&SiteID=1
If you're interested in an alternative to the Maintenance Plans you could
have a look at a stored procedure based solution that I've made.
http://blog.ola.hallengren.com/blog/_archives/2008/1/1/3440068.html
Ola Hallengren
http://ola.hallengren.com
"Rupesh Mondal" wrote:

> I have sql server 2005 standard edition with service pack 2(9.0.3050),when i
> am creating new maintainance plan ,at the end when i click finish button of
> the wizard,message i am getting is "one or more arguments are invalid",please
> reply me what is the problem asap.
> Thanks
> Rupesh
|||Thank you for the help, my sa password was blank thats why it was not working,
now it is working fine.
Rupesh Mondal.
"Ola Hallengren" wrote:
[vbcol=seagreen]
> It looks like some other people have been experiencing this problem. One
> thing that has been suggested in another thread is to assure that you have
> SP2 also of Management Studio.
> http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1823734&SiteID=1
> If you're interested in an alternative to the Maintenance Plans you could
> have a look at a stored procedure based solution that I've made.
> http://blog.ola.hallengren.com/blog/_archives/2008/1/1/3440068.html
> Ola Hallengren
> http://ola.hallengren.com
>
> "Rupesh Mondal" wrote:

Maintaintance plan error

I have sql server 2005 standard edition with service pack 2(9.0.3050),when i
am creating new maintainance plan ,at the end when i click finish button of
the wizard,message i am getting is "one or more arguments are invalid",please
reply me what is the problem asap.
Thanks
RupeshIt looks like some other people have been experiencing this problem. One
thing that has been suggested in another thread is to assure that you have
SP2 also of Management Studio.
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1823734&SiteID=1
If you're interested in an alternative to the Maintenance Plans you could
have a look at a stored procedure based solution that I've made.
http://blog.ola.hallengren.com/blog/_archives/2008/1/1/3440068.html
Ola Hallengren
http://ola.hallengren.com
"Rupesh Mondal" wrote:
> I have sql server 2005 standard edition with service pack 2(9.0.3050),when i
> am creating new maintainance plan ,at the end when i click finish button of
> the wizard,message i am getting is "one or more arguments are invalid",please
> reply me what is the problem asap.
> Thanks
> Rupesh|||Thank you for the help, my sa password was blank thats why it was not working,
now it is working fine.
Rupesh Mondal.
"Ola Hallengren" wrote:
> It looks like some other people have been experiencing this problem. One
> thing that has been suggested in another thread is to assure that you have
> SP2 also of Management Studio.
> http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1823734&SiteID=1
> If you're interested in an alternative to the Maintenance Plans you could
> have a look at a stored procedure based solution that I've made.
> http://blog.ola.hallengren.com/blog/_archives/2008/1/1/3440068.html
> Ola Hallengren
> http://ola.hallengren.com
>
> "Rupesh Mondal" wrote:
> > I have sql server 2005 standard edition with service pack 2(9.0.3050),when i
> > am creating new maintainance plan ,at the end when i click finish button of
> > the wizard,message i am getting is "one or more arguments are invalid",please
> > reply me what is the problem asap.
> >
> > Thanks
> > Rupesh

Monday, March 12, 2012

maint plan with syntax error from wizard

Hello,
I have created a fairly full-blown maint plan for a number of databases on
sql server standard 2005. The plan includes backup, index maintenance,
shrink, and a few other things I can't recall. This plan was created with
the maintenance wizard. When I try to run it I get a syntax error and in
viewing the generated t-sql I really don't see any problems with it. Has
anyone encountered this and what is the likely issue here? I guess I'm
implying that I don't really believe the error message since I don't believe
the wizard could really create a syntax error. Any help with this would be
greatly appreciated.
Thanks, NWOP.What is the T-SQL statement and the error messages?
By the way running shrink statements in your jobs and maintenance plan is
not a good idea and could impact the performance of your server.
Hope this helps,
Ben Nevarez
"new_world_order_pigs" wrote:
> Hello,
> I have created a fairly full-blown maint plan for a number of databases on
> sql server standard 2005. The plan includes backup, index maintenance,
> shrink, and a few other things I can't recall. This plan was created with
> the maintenance wizard. When I try to run it I get a syntax error and in
> viewing the generated t-sql I really don't see any problems with it. Has
> anyone encountered this and what is the likely issue here? I guess I'm
> implying that I don't really believe the error message since I don't believe
> the wizard could really create a syntax error. Any help with this would be
> greatly appreciated.
> Thanks, NWOP.|||Wow, you responded before the original showed up in the page. Thanks. The
only error message at all is "syntax error" and something along the lines of
job couldn't start. The only way I know to see the syntax is to "edit" the
step and click "show t-sql"-- if there is another way I'd like to know it and
also, if there are further error messages to look at I'd like to know that as
well.
Thanks again Ben,
NWOP.
"Ben Nevarez" wrote:
> What is the T-SQL statement and the error messages?
> By the way running shrink statements in your jobs and maintenance plan is
> not a good idea and could impact the performance of your server.
> Hope this helps,
> Ben Nevarez
>
>
> "new_world_order_pigs" wrote:
> > Hello,
> >
> > I have created a fairly full-blown maint plan for a number of databases on
> > sql server standard 2005. The plan includes backup, index maintenance,
> > shrink, and a few other things I can't recall. This plan was created with
> > the maintenance wizard. When I try to run it I get a syntax error and in
> > viewing the generated t-sql I really don't see any problems with it. Has
> > anyone encountered this and what is the likely issue here? I guess I'm
> > implying that I don't really believe the error message since I don't believe
> > the wizard could really create a syntax error. Any help with this would be
> > greatly appreciated.
> > Thanks, NWOP.|||If you have a problem with a job, select View History, expand the steps of
your job and look for error messages there. Also, some T-SQL statements write
entries to the SQL Server error log, so look for errors there as well.
Hope this helps,
Ben Nevarez
"new_world_order_pigs" wrote:
> Wow, you responded before the original showed up in the page. Thanks. The
> only error message at all is "syntax error" and something along the lines of
> job couldn't start. The only way I know to see the syntax is to "edit" the
> step and click "show t-sql"-- if there is another way I'd like to know it and
> also, if there are further error messages to look at I'd like to know that as
> well.
> Thanks again Ben,
> NWOP.
> "Ben Nevarez" wrote:
> >
> > What is the T-SQL statement and the error messages?
> >
> > By the way running shrink statements in your jobs and maintenance plan is
> > not a good idea and could impact the performance of your server.
> >
> > Hope this helps,
> >
> > Ben Nevarez
> >
> >
> >
> >
> > "new_world_order_pigs" wrote:
> >
> > > Hello,
> > >
> > > I have created a fairly full-blown maint plan for a number of databases on
> > > sql server standard 2005. The plan includes backup, index maintenance,
> > > shrink, and a few other things I can't recall. This plan was created with
> > > the maintenance wizard. When I try to run it I get a syntax error and in
> > > viewing the generated t-sql I really don't see any problems with it. Has
> > > anyone encountered this and what is the likely issue here? I guess I'm
> > > implying that I don't really believe the error message since I don't believe
> > > the wizard could really create a syntax error. Any help with this would be
> > > greatly appreciated.
> > > Thanks, NWOP.|||Ben Nevarez wrote:
> If you have a problem with a job, select View History, expand the steps of
> your job and look for error messages there. Also, some T-SQL statements write
> entries to the SQL Server error log, so look for errors there as well.
> Hope this helps,
> Ben Nevarez
>
>
> "new_world_order_pigs" wrote:
>
>> Wow, you responded before the original showed up in the page. Thanks. The
>> only error message at all is "syntax error" and something along the lines of
>> job couldn't start. The only way I know to see the syntax is to "edit" the
>> step and click "show t-sql"-- if there is another way I'd like to know it and
>> also, if there are further error messages to look at I'd like to know that as
>> well.
>> Thanks again Ben,
>> NWOP.
>> "Ben Nevarez" wrote:
>>
>> What is the T-SQL statement and the error messages?
>> By the way running shrink statements in your jobs and maintenance plan is
>> not a good idea and could impact the performance of your server.
>> Hope this helps,
>> Ben Nevarez
>>
>>
>> "new_world_order_pigs" wrote:
>>
>> Hello,
>> I have created a fairly full-blown maint plan for a number of databases on
>> sql server standard 2005. The plan includes backup, index maintenance,
>> shrink, and a few other things I can't recall. This plan was created with
>> the maintenance wizard. When I try to run it I get a syntax error and in
>> viewing the generated t-sql I really don't see any problems with it. Has
>> anyone encountered this and what is the likely issue here? I guess I'm
>> implying that I don't really believe the error message since I don't believe
>> the wizard could really create a syntax error. Any help with this would be
>> greatly appreciated.
>> Thanks, NWOP.
Since this is a maintenance plan - right click on the maintenance plan
and view history instead of the agent job. This history will show you
each step in your maintenance plan and give you more information about
what exactly is failing.|||Hello again and thanks for all the assistance. I have now done all of these
things and actually taken each and every step separately, viewed the t-sql,
executed it step by step and get a success on each one. So, I'm thinking it
must be something having to do with the manner in which it is evoked. I
guess I'm still surprised this isn't a common and recognizeable problem since
I've never believed that I'm "so special." In any case, where would I look
to see how the job itself is being invoked? Perhaps that is it? Perhaps I'm
missing something?
Thanks again,
NWOP.
"Jeffrey Williams" wrote:
> Ben Nevarez wrote:
> > If you have a problem with a job, select View History, expand the steps of
> > your job and look for error messages there. Also, some T-SQL statements write
> > entries to the SQL Server error log, so look for errors there as well.
> >
> > Hope this helps,
> >
> > Ben Nevarez
> >
> >
> >
> >
> > "new_world_order_pigs" wrote:
> >
> >
> >> Wow, you responded before the original showed up in the page. Thanks. The
> >> only error message at all is "syntax error" and something along the lines of
> >> job couldn't start. The only way I know to see the syntax is to "edit" the
> >> step and click "show t-sql"-- if there is another way I'd like to know it and
> >> also, if there are further error messages to look at I'd like to know that as
> >> well.
> >>
> >> Thanks again Ben,
> >> NWOP.
> >>
> >> "Ben Nevarez" wrote:
> >>
> >>
> >> What is the T-SQL statement and the error messages?
> >>
> >> By the way running shrink statements in your jobs and maintenance plan is
> >> not a good idea and could impact the performance of your server.
> >>
> >> Hope this helps,
> >>
> >> Ben Nevarez
> >>
> >>
> >>
> >>
> >> "new_world_order_pigs" wrote:
> >>
> >>
> >> Hello,
> >>
> >> I have created a fairly full-blown maint plan for a number of databases on
> >> sql server standard 2005. The plan includes backup, index maintenance,
> >> shrink, and a few other things I can't recall. This plan was created with
> >> the maintenance wizard. When I try to run it I get a syntax error and in
> >> viewing the generated t-sql I really don't see any problems with it. Has
> >> anyone encountered this and what is the likely issue here? I guess I'm
> >> implying that I don't really believe the error message since I don't believe
> >> the wizard could really create a syntax error. Any help with this would be
> >> greatly appreciated.
> >> Thanks, NWOP.
> >>
> Since this is a maintenance plan - right click on the maintenance plan
> and view history instead of the agent job. This history will show you
> each step in your maintenance plan and give you more information about
> what exactly is failing.
>

Friday, March 9, 2012

Main differences between new Express Report Server and Standard one?

So far, I haven't been able to find a good list of what the major differences are between the express Reporting Server and the standard one. We are developing an application that will be doing the reporting through SQL server reporting services. Some of our smaller clients will be using SQL Server express instead of enterprise or standard. Anything majorly different in the Express version?

Check out this link - http://www.microsoft.com/sql/technologies/reporting/rsfeatures.mspx

Thanks,

Sharmila

|||Thanks for the reply.

I did see that comparison matrix earlier before the Express Reporting was actually relased. It seemed that they did make some changes from what they were going to do originally. I was hoping there was an up to date feature matrix as that one you linked to mentions that the reporting services still aren't available. I figure there may have been a few changes between then and now
|||

Reporting services is now available in Express with Advanced Services and the following article details that. Hope this helps.

http://msdn2.microsoft.com/en-us/library/ms365166(SQL.90).aspx

Sharmila

Wednesday, March 7, 2012

MAIL on SQL Server 2000 Standard on Windows Server 2003 64-bit

I've read about 2005 Enterprise Edition 64-bit and 2000 Enterprise Edition 64-bit and those mail issues. But, my particular situation is running SQL Server 2000 Standard Edition (32-bit) on Windows 2003 Server (64-bit). I got the mail profile set up ok for the SQL Server Service Account using Outlook 2000 and can send and receive mail using Outlook. But, even after restarting the SQL Server Services, there's no profile to choose in the SQL Mail or Agent Mail drop-down box. I have tried ON the server and remotely. Locally, the drop-down box doesn't even really 'drop down'. Remotely, I get the drop-down but it is empty. I don't need a primer on configuring SQL Mail for SQL 2000. I just need to know if this combination of SQL Server Editions and OS Editions will even support SQL Mail. Maybe adding the appropriate values in the registry will enable me to use this mail profile for SQL Server?
What about that smtp client that's out there. I've not used it on any machine and don't want to make this goofy one the guinea pig if it hasn't been proven to work.
No, we can't go to SQL Server 2005 yet on this server. It hosts a purchased system that isn't supported on SQL Server 2005.
Thanks for your help,
Michelle
I rebooted the server and was able to configure the mail profile and select it from my client/enterprise manager. It seems like things generally require a reboot more often on this server than I've experienced on other servers. I tested agent mail, xp_sendamail, and dts send mail tasks all to success. Now I'm fighting with installation of the SQL Server Health & History Tool.
Just wanted to document that sql mail DOES seem to work with this configuration. Keep trying and I'm sure that you'll get it to work, too :)

Monday, February 20, 2012

MAC Address attribute

Hi:

I need to store MAC Addresses. What is the standard way of storing this
type of attribute? Datatype? I can't find any discussions about this
anywhere.

Thx for any pointers.A MAC address is a binary value. You could store these using a binary data
type (binary or varbinary) or store the hex string notation in a character
datatype (char or varchar). One advantage of a binary data type is lower
space requirements and an advantage of a character data type is that it's a
bit easier to display by application programs.

--
Hope this helps.

Dan Guzman
SQL Server MVP

"xAvailx" <bjzamora@.hotmail.com> wrote in message
news:1123625751.632127.142510@.g43g2000cwa.googlegr oups.com...
> Hi:
> I need to store MAC Addresses. What is the standard way of storing this
> type of attribute? Datatype? I can't find any discussions about this
> anywhere.
> Thx for any pointers.

LSN Issues..

As a standard backup plan I am making Full backup, differential backup and
transactional backup. I had some instances where the SQL Server was throwing
error while restoring the transaction log related to log serial number. Some
thing it was saying too early to restore.. Or restore the previous log
before restoring this.
Anybody suggest me on what considerations I should make not to break this
LSN?
In summary, what jobs or routine that I should not run to make sure that my
transactional logs are recoverable?
SQL 2K.
Thanks
SmithIf you stay in full (or bulk logged) recovery mode, then it shouldn't be abl
e to break the log chain
sequence. If you see such a case, you have hit a bug in SQL Server and it is
time to hunt KB and
possibly open a case with MS Support.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Smith" <Hose_smith_Ireland@.hotmail.com> wrote in message
news:%23EAZvJrcFHA.4040@.TK2MSFTNGP10.phx.gbl...
> As a standard backup plan I am making Full backup, differential backup and
> transactional backup. I had some instances where the SQL Server was throwi
ng
> error while restoring the transaction log related to log serial number. So
me
> thing it was saying too early to restore.. Or restore the previous log
> before restoring this.
> Anybody suggest me on what considerations I should make not to break this
> LSN?
> In summary, what jobs or routine that I should not run to make sure that m
y
> transactional logs are recoverable?
> SQL 2K.
> Thanks
> Smith
>|||Thanks for your answer.
One more clarification,
when you say "If you stay in full (or bulk logged) recovery mode", does it
means that after fullbackup I should not switch between recovery modes? Let
us say I switch between recovery modes (full or bulk logged) If I take a
fullbackup should it be fine?
or
After switching between should I restart the SQL Server service?
Thanks,
Smith
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:OKQ$lwwcFHA.612@.TK2MSFTNGP12.phx.gbl...
> If you stay in full (or bulk logged) recovery mode, then it shouldn't be
able to break the log chain
> sequence. If you see such a case, you have hit a bug in SQL Server and it
is time to hunt KB and
> possibly open a case with MS Support.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Smith" <Hose_smith_Ireland@.hotmail.com> wrote in message
> news:%23EAZvJrcFHA.4040@.TK2MSFTNGP10.phx.gbl...
and[vbcol=seagreen]
throwing[vbcol=seagreen]
Some[vbcol=seagreen]
this[vbcol=seagreen]
my[vbcol=seagreen]
>|||You can switch between full and bulk logged. But if you go to simple, you br
eak the log chain
sequence. No need to restart.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Smith" <Hose_smith_Ireland@.hotmail.com> wrote in message
news:%23945kL2cFHA.3488@.tk2msftngp13.phx.gbl...
> Thanks for your answer.
> One more clarification,
> when you say "If you stay in full (or bulk logged) recovery mode", does it
> means that after fullbackup I should not switch between recovery modes? Le
t
> us say I switch between recovery modes (full or bulk logged) If I take a
> fullbackup should it be fine?
> or
> After switching between should I restart the SQL Server service?
> Thanks,
> Smith
>
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote i
n
> message news:OKQ$lwwcFHA.612@.TK2MSFTNGP12.phx.gbl...
> able to break the log chain
> is time to hunt KB and
> and
> throwing
> Some
> this
> my
>

LSN Issues..

As a standard backup plan I am making Full backup, differential backup and
transactional backup. I had some instances where the SQL Server was throwing
error while restoring the transaction log related to log serial number. Some
thing it was saying too early to restore.. Or restore the previous log
before restoring this.
Anybody suggest me on what considerations I should make not to break this
LSN?
In summary, what jobs or routine that I should not run to make sure that my
transactional logs are recoverable?
SQL 2K.
Thanks
Smith
If you stay in full (or bulk logged) recovery mode, then it shouldn't be able to break the log chain
sequence. If you see such a case, you have hit a bug in SQL Server and it is time to hunt KB and
possibly open a case with MS Support.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Smith" <Hose_smith_Ireland@.hotmail.com> wrote in message
news:%23EAZvJrcFHA.4040@.TK2MSFTNGP10.phx.gbl...
> As a standard backup plan I am making Full backup, differential backup and
> transactional backup. I had some instances where the SQL Server was throwing
> error while restoring the transaction log related to log serial number. Some
> thing it was saying too early to restore.. Or restore the previous log
> before restoring this.
> Anybody suggest me on what considerations I should make not to break this
> LSN?
> In summary, what jobs or routine that I should not run to make sure that my
> transactional logs are recoverable?
> SQL 2K.
> Thanks
> Smith
>
|||Thanks for your answer.
One more clarification,
when you say "If you stay in full (or bulk logged) recovery mode", does it
means that after fullbackup I should not switch between recovery modes? Let
us say I switch between recovery modes (full or bulk logged) If I take a
fullbackup should it be fine?
or
After switching between should I restart the SQL Server service?
Thanks,
Smith
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:OKQ$lwwcFHA.612@.TK2MSFTNGP12.phx.gbl...
> If you stay in full (or bulk logged) recovery mode, then it shouldn't be
able to break the log chain
> sequence. If you see such a case, you have hit a bug in SQL Server and it
is time to hunt KB and[vbcol=seagreen]
> possibly open a case with MS Support.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Smith" <Hose_smith_Ireland@.hotmail.com> wrote in message
> news:%23EAZvJrcFHA.4040@.TK2MSFTNGP10.phx.gbl...
and[vbcol=seagreen]
throwing[vbcol=seagreen]
Some[vbcol=seagreen]
this[vbcol=seagreen]
my
>
|||You can switch between full and bulk logged. But if you go to simple, you break the log chain
sequence. No need to restart.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Smith" <Hose_smith_Ireland@.hotmail.com> wrote in message
news:%23945kL2cFHA.3488@.tk2msftngp13.phx.gbl...
> Thanks for your answer.
> One more clarification,
> when you say "If you stay in full (or bulk logged) recovery mode", does it
> means that after fullbackup I should not switch between recovery modes? Let
> us say I switch between recovery modes (full or bulk logged) If I take a
> fullbackup should it be fine?
> or
> After switching between should I restart the SQL Server service?
> Thanks,
> Smith
>
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
> message news:OKQ$lwwcFHA.612@.TK2MSFTNGP12.phx.gbl...
> able to break the log chain
> is time to hunt KB and
> and
> throwing
> Some
> this
> my
>

LSN Issues..

As a standard backup plan I am making Full backup, differential backup and
transactional backup. I had some instances where the SQL Server was throwing
error while restoring the transaction log related to log serial number. Some
thing it was saying too early to restore.. Or restore the previous log
before restoring this.
Anybody suggest me on what considerations I should make not to break this
LSN?
In summary, what jobs or routine that I should not run to make sure that my
transactional logs are recoverable?
SQL 2K.
Thanks
SmithIf you stay in full (or bulk logged) recovery mode, then it shouldn't be able to break the log chain
sequence. If you see such a case, you have hit a bug in SQL Server and it is time to hunt KB and
possibly open a case with MS Support.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Smith" <Hose_smith_Ireland@.hotmail.com> wrote in message
news:%23EAZvJrcFHA.4040@.TK2MSFTNGP10.phx.gbl...
> As a standard backup plan I am making Full backup, differential backup and
> transactional backup. I had some instances where the SQL Server was throwing
> error while restoring the transaction log related to log serial number. Some
> thing it was saying too early to restore.. Or restore the previous log
> before restoring this.
> Anybody suggest me on what considerations I should make not to break this
> LSN?
> In summary, what jobs or routine that I should not run to make sure that my
> transactional logs are recoverable?
> SQL 2K.
> Thanks
> Smith
>|||Thanks for your answer.
One more clarification,
when you say "If you stay in full (or bulk logged) recovery mode", does it
means that after fullbackup I should not switch between recovery modes? Let
us say I switch between recovery modes (full or bulk logged) If I take a
fullbackup should it be fine?
or
After switching between should I restart the SQL Server service?
Thanks,
Smith
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:OKQ$lwwcFHA.612@.TK2MSFTNGP12.phx.gbl...
> If you stay in full (or bulk logged) recovery mode, then it shouldn't be
able to break the log chain
> sequence. If you see such a case, you have hit a bug in SQL Server and it
is time to hunt KB and
> possibly open a case with MS Support.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Smith" <Hose_smith_Ireland@.hotmail.com> wrote in message
> news:%23EAZvJrcFHA.4040@.TK2MSFTNGP10.phx.gbl...
> > As a standard backup plan I am making Full backup, differential backup
and
> > transactional backup. I had some instances where the SQL Server was
throwing
> > error while restoring the transaction log related to log serial number.
Some
> > thing it was saying too early to restore.. Or restore the previous log
> > before restoring this.
> >
> > Anybody suggest me on what considerations I should make not to break
this
> > LSN?
> >
> > In summary, what jobs or routine that I should not run to make sure that
my
> > transactional logs are recoverable?
> >
> > SQL 2K.
> >
> > Thanks
> >
> > Smith
> >
> >
>|||You can switch between full and bulk logged. But if you go to simple, you break the log chain
sequence. No need to restart.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Smith" <Hose_smith_Ireland@.hotmail.com> wrote in message
news:%23945kL2cFHA.3488@.tk2msftngp13.phx.gbl...
> Thanks for your answer.
> One more clarification,
> when you say "If you stay in full (or bulk logged) recovery mode", does it
> means that after fullbackup I should not switch between recovery modes? Let
> us say I switch between recovery modes (full or bulk logged) If I take a
> fullbackup should it be fine?
> or
> After switching between should I restart the SQL Server service?
> Thanks,
> Smith
>
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
> message news:OKQ$lwwcFHA.612@.TK2MSFTNGP12.phx.gbl...
>> If you stay in full (or bulk logged) recovery mode, then it shouldn't be
> able to break the log chain
>> sequence. If you see such a case, you have hit a bug in SQL Server and it
> is time to hunt KB and
>> possibly open a case with MS Support.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "Smith" <Hose_smith_Ireland@.hotmail.com> wrote in message
>> news:%23EAZvJrcFHA.4040@.TK2MSFTNGP10.phx.gbl...
>> > As a standard backup plan I am making Full backup, differential backup
> and
>> > transactional backup. I had some instances where the SQL Server was
> throwing
>> > error while restoring the transaction log related to log serial number.
> Some
>> > thing it was saying too early to restore.. Or restore the previous log
>> > before restoring this.
>> >
>> > Anybody suggest me on what considerations I should make not to break
> this
>> > LSN?
>> >
>> > In summary, what jobs or routine that I should not run to make sure that
> my
>> > transactional logs are recoverable?
>> >
>> > SQL 2K.
>> >
>> > Thanks
>> >
>> > Smith
>> >
>> >
>>
>

Wednesday, March 28, 2012

Maintenance plan error in SQL Server 2000(SP3) Standard Ed!

Maintenance Plan Error

Maintenance Plan Configuration

Maintenance Plan Configuration

Maintenance Plan Configuration

Friday, March 23, 2012

Maintenance Cleanup Task……

Maintenance Cleanup Task……

Maintenance Cleanup Task……

Maintenance Cleanup Task……

Monday, March 19, 2012

Maintaintance plan error

Maintaintance plan error

Monday, March 12, 2012

maint plan with syntax error from wizard

Friday, March 9, 2012

Main differences between new Express Report Server and Standard one?

Wednesday, March 7, 2012

MAIL on SQL Server 2000 Standard on Windows Server 2003 64-bit

Monday, February 20, 2012

MAC Address attribute

LSN Issues..

LSN Issues..

LSN Issues..

Lowering priority

Blog Archive

About Me